site

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

With no annotations provided, the description carries the full behavioral burden. It clearly discloses that nothing is bought, ordered, or paid, that no quote is guaranteed, that the service is free, and what information is returned. This gives the agent a strong safety and expectations profile without needing 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 three sentences with no fluff. 'Read first' front-loads the key usage instruction, and every subsequent sentence adds distinct value: what the tool explains, what does not happen, and what specific information is returned.

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 informational tool, this description is complete. It explains the tool's role, the domain, the non-transactional guarantees, and enumerates the returned content (who receives details, consent wording, confirmation mechanism). No output schema exists, but the description provides sufficient detail for correct use.

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 zero parameters and the description appropriately mentions none. Since the tool requires no input, the baseline of 4 applies; there is no parameter information that the description would need to add.

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 on Clinical Waste Quotes. It clearly distinguishes itself from the action tool by saying it 'states plainly' rather than performing the enquiry, and the title reinforces that it is informational, not transactional.

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' explicitly tells the agent to use this before other actions, and the description names submit_enquiry as the subject it explains. It does not mention enquiry_fields as an alternative, but the context is clear enough for an agent to understand this is the preparatory/explainer tool.

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 burden of behavioral disclosure. It transparently enumerates the returned data elements and implies a read-only introspection operation, but it does not explicitly state side-effect profile, response wrapping, or error behavior. This is adequate but not rich.

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 two compact sentences with no filler. The first sentence front-loads the resource and content list; the second sentence gives directly actionable guidance for using the results with a sibling tool.

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, one-purpose metadata tool, the description covers what is returned and how to use the result. It is nearly complete, though it could have been stronger with an explicit note that this is a read-only metadata lookup or a more direct naming of enquiry_describe as the alternative for higher-level enquiry information.

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 full schema description coverage, so the baseline is 4. The description adds the important semantic that field keys are the linking mechanism for submit_enquiry, which supports correct usage even though there are no params 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 identifies the resource ('Every field of the Clinical Waste Quotes enquiry') and specifies the exact attributes returned: key, label, type, required, help text, and allowed options. It lacks an explicit verb like 'returns' or 'lists', and it does not directly contrast itself with enquiry_describe, though it is recognizably distinct from submit_enquiry.

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 provides clear usage context by stating that answers should be passed to submit_enquiry keyed by field key, establishing a workflow. It does not explicitly say when to avoid this tool or how it differs from enquiry_describe, so it falls just short of full guidance.

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 present, the description carries the full burden and explains the side effects and gating behavior: validation on step 1, an email with a clickable link on step 2, and no provider visibility until the link is clicked. The exact consent statement is quoted, so the agent can confirm user consent correctly.

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 because the tool has a two-step flow and a consent requirement that cannot be compressed further. The key warnings are front-loaded at the beginning so an agent sees the non-purchase nature immediately.

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 multi-step submission tool with no output schema and no annotations, the description is complete: it defines the preconditions, the exact consent text, the step-1 return values, the step-2 continuation condition, and the post-submission email requirement. No critical operational detail appears to be 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?

Although the schema already describes all three parameters, the description adds workflow semantics: answers must be keyed by field key from enquiry_fields, consent must be true in both steps, and confirmation is the token returned in step 1 and required only for the second call. This mapping is materially more useful than the bare schema fields.

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 action and resource: submits an enquiry to Clinical Waste Quotes, and immediately excludes look-alike intent by saying it is NOT a purchase or guaranteed quote. It also references enquiry_fields as the source of answer keys, which orients the agent among 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 an explicit two-step protocol: call once with answers and consent=true to get a summary and confirmation token, then call again only after the person agrees, using the same answers and the token. This tells the agent exactly when to make each call and what must happen between calls.

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