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

With no annotations provided, the description carries the full disclosure burden. It usefully describes the response content and the conditional nature of allowed options ('where there are any'), but it never explicitly states that this is a read-only introspection call, nor does it disclose ordering, caching, or failure behavior.

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 dense sentences with zero filler. The first states what is returned; the second adds the downstream usage payload. Both earn their place.

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 metadata-listing tool with no output schema, the description explains what the return carries and how it feeds into submit_enquiry. It could add an example or enumerate the 'type' values, but nothing essential is missing for invoking the tool 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?

The tool has zero parameters and 100% (vacuously) schema coverage, so there are no input semantics to clarify. The description's 'Every field' phrasing correctly implies an unfiltered, all-fields response, which is consistent with an empty input 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 clearly identifies the resource ('Every field of the Toll Blenders enquiry') and enumerates its contents (key, label, type, required, help text, allowed options). The verb is only implied by the tool name rather than stated, and it doesn't differentiate from enquiry_describe, but the overall purpose is unambiguous.

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 second sentence provides concrete usage guidance: obtain field keys here, then pass answers to submit_enquiry keyed by those keys. This tells the agent when this tool is needed in the workflow, though it does not explicitly exclude alternatives or name 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.