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

With no annotations, the description carries the disclosure burden and does it well: it states that nothing is bought, ordered or paid, no quote is guaranteed, and it is free. It also discloses the content of the return (recipients, consent wording, confirmation), although it does not explicitly mark the tool as read-only.

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 brief and front-loads the most important instruction ('Read first') and the core clarification about what submission really means. The sentences are compact, though the 'Also returns' clause is a bit compressed.

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 no output schema and no parameters, the description covers the essential context an agent needs: the nature of the enquiry, the absence of payment/quote guarantees, and the content returned. It could add an explicit statement about the tool's own output, but it is largely complete for a zero-parameter explainer.

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. The description adds useful semantic context about what the submission entails and what information is returned, compensating fully for the empty 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 names a specific verb ('states plainly'), a resource ('what submit_enquiry does on HGV Hours Calculator'), and distinguishes it from the actual submission tool by clarifying that no purchase or quote is involved. It clearly positions enquiry_describe as the explanatory companion to submit_enquiry among 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?

'Read first' explicitly tells the agent when to invoke this tool, before using submit_enquiry. It does not spell out exclusions relative to calculator_describe or enquiry_fields, but the positioning is clear enough for routing.

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