site

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

With no annotations, the description carries the burden and does well: it explicitly states that nothing is bought, ordered, or paid, that no quote is guaranteed, and that it is free. It also discloses the return content. It could more explicitly state that enquiry_describe itself performs no submission, but the 'Read first' framing makes this reasonably clear.

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?

Three sentences with front-loaded 'Read first' and a compact summary of the tool's output. Minor redundancy between 'Nothing is bought, ordered or paid' and 'it is free,' but the text is appropriately sized and structured for quick scanning.

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, no-output-schema helper tool, the description is complete: it explains the purpose, sets behavioral expectations, and lists exactly what information is returned. An agent has enough context to invoke it and interpret the result.

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 a 100% schema-covered empty schema, so the baseline is 4. The description adds useful context about what the returned explanation covers, which is more than needed for parameter semantics.

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 identifies the tool as a read-first explainer: it 'states plainly what submit_enquiry does' on ISO Certification Cost and enumerates the returned content (who receives details, consent wording, confirmation). This differentiates it from the actual submission sibling submit_enquiry, and the title reinforces that the result is an enquiry, 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?

'Read first' is a direct cue to use this tool before taking any action, which implicitly distinguishes it from submit_enquiry. It does not explicitly reference the enquiry_fields sibling or state when not to use it, but the purpose and timing are clear enough.

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?

No annotations are present, so the description carries the behavioral disclosure burden. It reveals the output shape (key, label, type, required, help text, options) and implies a read-only retrieval behavior. It does not discuss errors, permissions, or side effects, but for a parameterless field-listing tool this is reasonably transparent.

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 carry all necessary information: the first defines what fields are returned and the second explains how to use them. There is no filler, and the most important detail—what the tool provides—is front-loaded.

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 compensates well by enumerating the return fields and linking to the downstream submit_enquiry workflow. It is complete enough to call the tool correctly, though it leaves the sibling enquiry_describe unaddressed, which is a minor gap given the sibling list.

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 an empty input schema, so there are no parameter semantics to document. The zero-parameter baseline is 4, and the description appropriately focuses on the returned data rather than inputs.

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 resource ('every field of the ISO Certification Cost enquiry') and lists the exact contents (key, label, type, required, help text, allowed options). It also separates this tool from submit_enquiry by telling the agent that answers go there keyed by field key. This is a clear, specific definition that names what the tool exposes.

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 a clear workflow: obtain fields here, then pass answers to submit_enquiry keyed by field key. This tells the agent when to use the tool relative to one sibling. It does not mention enquiry_describe or explicitly state when not to use this tool, so it lacks full alternative exclusion but provides solid context.

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 full responsibility for behavioral disclosure, and it does so thoroughly. It discloses the two-step validation behavior, the confirmation token, the consent wording, the email with a click link, and the fact that providers only see the enquiry after the link is clicked. This is unusually transparent for a tool with no annotations.

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 longer than average, but every sentence earns its place given the two-step complexity. It is well-structured with explicit 'Step 1' and 'Step 2' markers, front-loads the most important caveat ('not a purchase'), and avoids filler while retaining all essential workflow details.

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?

Given the tool's complexity, the absence of annotations, and the lack of an output schema, the description is remarkably complete. It explains what the caller receives after Step 1, what conditions must be met for Step 2, what happens after submission, and how the consent check works. The only minor omission is a formal response schema, but the description narratively covers the return values.

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?

Even though the schema already provides descriptions for all parameters, the description adds crucial semantics: answers must be keyed by field keys from enquiry_fields, consent must match the exact quoted legal line, and confirmation is the token returned in Step 1. This goes beyond the schema by explaining the relationship between parameters and the two-step workflow.

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 verb and resource: 'Submits an enquiry to ISO Certification Cost.' It also clarifies what the tool is not ('NOT a purchase, NOT a guaranteed quote') and emphasizes the two-step flow, making the tool's purpose unmistakable and distinct from the sibling tools.

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 usage instructions: Step 1 with answers and consent=true to receive a summary and token, then Step 2 only after the person agrees, reusing the token. It also sets a clear exclusion ('not a purchase') and explains the required consent condition, leaving no ambiguity about when and how to invoke the tool.

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