site

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

No annotations are present, so the description carries the behavioral burden. It does disclose what the output contains ('who receives the details, the consent wording, and how the person confirms') and clarifies the outcome is free with no purchase or guaranteed quote. However, it never explicitly states the tool itself is read-only or non-mutating, and some clauses describe submit_enquiry's behavior rather than enquiry_describe's, leaving slight ambiguity about side effects.

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 front-loaded with the key instruction ('Read first') and purpose, then adds useful output details in three sentences. Minor deduction because the title and description both repeat 'not a purchase / not a guaranteed quote', and the specific page name 'Campervan Conversion Cost' adds limited invocation value.

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?

With no output schema, the description sufficiently covers what the tool returns and frames it as a pre-submission explanation of submit_enquiry. It is slightly incomplete about the exact output format and the relationship to enquiry_fields, but for a zero-parameter informational tool, the description is largely complete.

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 has zero parameters and the schema already reflects that, so there is no parameter burden for the description to carry. The baseline of 4 for a no-parameter tool applies; the description adds no parameter-specific meaning because none is needed.

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 names a specific verb and resource: it 'States plainly what submit_enquiry does', which clearly positions enquiry_describe as an informational tool rather than the action tool. It also references sibling submit_enquiry, helping an agent distinguish them. However, the title 'What you get: an ENQUIRY with a human' could be misread as the tool itself creating an enquiry, and the description never explicitly says 'this tool does not submit'.

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' is a clear usage signal that this tool should be used before submit_enquiry, and naming submit_enquiry as the subject being described gives the agent an obvious alternative. It does not discuss the other sibling, enquiry_fields, nor give explicit when-not-to-use conditions, so it stops short of a 5.

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 must carry the behavioral burden. It transparently describes the output content and the relationship to submit_enquiry, and it implies a read-only metadata lookup. It does not explicitly state that the operation is read-only or describe response format, but for this simple field-listing tool the disclosed behavior is adequate.

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 a single dense sentence that front-loads the core meaning and contains no filler. Every clause earns its place: the resource, the fields covered, and the downstream usage instruction.

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 no-parameter, schema-less metadata tool, the description covers the key information an agent needs: what data is returned, what attributes are included, and how the result connects to submit_enquiry. It is slightly incomplete in not clarifying how this relates to enquiry_describe or describing the exact response container, but these are minor gaps 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 has zero parameters, so the baseline is 4 as specified. The description adds relevant semantic context about how the tool's output should be used ('Pass answers to submit_enquiry keyed by field key'), even though there is no parameter surface to document.

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 clearly states that the tool exposes the fields of the Campervan Conversion Cost enquiry and enumerates the attributes included (key, label, type, required, help text, options). The title reinforces this meaning. It does not begin with an explicit verb like 'Lists' or 'Returns', and it does not contrast itself with enquiry_describe, so it stops short of full sibling differentiation.

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 indirect usage guidance by noting that answers should be submitted to submit_enquiry keyed by field key, implying this tool is used to discover valid keys. However, it does not explicitly say when to use this tool versus enquiry_describe or provide any exclusion criteria. Usage is implied rather than stated.

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 burden and does so thoroughly. It discloses validation behavior, the step 1 return values (summary, consent line, confirmation token), the requirement to show these to the user, and the step 2 outcome of an email with a link that providers only see after the link is clicked.

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 front-loaded with the core purpose and exclusions, then organized into Step 1 and Step 2 with no redundant sentences. The quoted consent text is long but necessary, and every sentence contributes either to the flow, the consent requirement, or the outcome.

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 or annotations, the description is complete enough to guide correct usage: it explains what step 1 returns, what to show the user, when to proceed, what to pass in step 2, and what happens after submission. An agent has all required information to orchestrate the two-step flow correctly.

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?

Since schema description coverage is 100%, baseline is 3. The description adds meaning by explaining the step sequencing: step 1 uses answers and consent=true, step 2 adds the confirmation token, and answers are keyed by field keys from enquiry_fields. It also reinforces the exact consent wording, going slightly 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 uses a specific verb and resource: 'Submits an enquiry to Campervan Conversion Cost' and explicitly clarifies what it is NOT ('NOT a purchase, NOT a guaranteed quote'). The two-step flow is described clearly, so the tool's role is unambiguous and easily distinguished from siblings like enquiry_describe and enquiry_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 explicit when-to-use instructions: call step 1 with answers and consent=true, then only call step 2 if the person agrees, passing the same answers, consent=true, and the confirmation token. It also provides a when-not via 'NOT a purchase' and explains the consent precondition with the exact line the person must have agreed to.

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