site

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations available, the description carries the behavioral disclosure burden. It clearly states that the tool returns information, clarifies the nature of the enquiry, and describes what the output covers: recipients, consent wording, and confirmation method. This is adequate transparency for a zero-parameter informational tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is compact and front-loaded with the most important instruction ('Read first'). Every sentence contributes distinct value: purpose, what is not happening, and what the tool returns. There is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-parameter describe tool with no output schema, the description fully covers what an agent needs: what the tool is for, how it relates to submit_enquiry, and what the returned information contains. Nothing important is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has no parameters, so schema coverage is effectively 100% and there is nothing for the description to add about parameter meaning. The baseline for zero-parameter tools applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific purpose: it explains what submit_enquiry does, rather than performing an enquiry. It also distinguishes itself from the sibling submit_enquiry tool by explicitly describing the nature of the outcome (an enquiry with human providers, not a purchase or guaranteed quote).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The opening 'Read first' gives a clear contextual signal that this tool should be used before acting, likely before submit_enquiry. It does not explicitly name alternatives or exclusions, but the intended usage context is clear enough for an agent.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden; it usefully discloses the returned field metadata and indirectly signals a read-only lookup by directing submissions to submit_enquiry. It does not explicitly state that it performs no side effects or describe output shape or error behavior, so transparency is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both purposeful: the first specifies the content, the second connects the output to the submission workflow. No filler or repetition.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter listing tool, the description covers what the agent receives and how to use it with submit_enquiry. It does not explicitly state the return container (e.g., array or object) or the role of enquiry_describe, but these are minor given the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the empty schema leaves nothing for the description to explain about inputs. The description adds relevant guidance by telling agents to use the returned field keys as the keying scheme for submit_enquiry, which is value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description concretely identifies the resource ('Glazier Prices enquiry') and enumerates exactly what is exposed: key, label, type, required, help text, and allowed options. It stops short of an explicit verb like 'returns' or 'lists', and the relationship to enquiry_describe is not clarified, so it is not a full 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the tool should be consulted before submit_enquiry by saying answers must be keyed by the returned field keys. It does not explicitly state when to prefer this over enquiry_describe or when not to use it.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full behavioral burden — and it delivers: it discloses the two-call validation flow, the email side effect with the mandatory link click before any provider sees the enquiry, the non-guarantee of a quote, and the exact consent semantics. This is exceptionally rich disclosure of side effects and sequencing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Four dense sentences, front-loaded with purpose and exclusions, with the two-step flow clearly labeled ('Step 1:', 'Step 2:'). It is appropriately sized for the tool's complexity and no sentence is wasted, though the repeated consent quote makes it slightly longer than necessary and a more scannable layout would help.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite having no output schema, the description covers the step-1 return shape (summary, consent line, confirmation token), the post-submission side effect (email with clickable link), the prerequisite (answers keyed from enquiry_fields), and the consent gate. The only omission is failure-mode handling, which is minor against this level of completeness.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the baseline is 3. The description adds temporal meaning the flat schema cannot express: the confirmation token only exists after step 1, the same answers must be reused, and consent=true is required in both calls. That flow-level context genuinely supplements the per-parameter schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource — 'Submits an enquiry to Glazier Prices' — and immediately constrains scope with negations ('NOT a purchase, NOT a guaranteed quote'). The title ('Submit an ENQUIRY to human providers (two steps; not a purchase)') plus the reference to enquiry_fields for answer keys clearly separates it from its siblings, which are about describing enquiries and listing fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives an explicit two-step invocation protocol: Step 1 with answers and consent=true to get a summary/token, and Step 2 'only if the person agrees' with the same answers plus the confirmation token. It states a when-not boundary ('NOT a purchase') and directs the agent to enquiry_fields for valid answer keys, leaving no ambiguity about how or when to call.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.