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.