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

With no annotations, the description carries the full burden and does meaningful work: it discloses that nothing is bought, ordered, or paid, that no quote is guaranteed, that it is free, and that it starts an enquiry with human providers who quote directly. It also signals the return contents (recipients, consent wording, confirmation). It stops short of stating side effects or auth requirements, but for a zero-param documentation tool that is a minor gap.

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?

'Read first' is front-loaded and the three sentences each carry content: the purpose, the transactional disclaimers, and the return contents. It is a touch repetitive ('Nothing is bought, ordered or paid' plus 'no quote is guaranteed; it is free'), but nothing is wasted enough to harm usability.

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?

There is no output schema, so the description must cover returns, and it does: recipients, consent wording, and how the person confirms. Combined with the safety/expectation disclaimers, an agent has enough to decide when to call it and what to expect back. A short note on ordering relative to enquiry_fields would make it complete.

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 takes no parameters (schema coverage 100% of an empty object), so the baseline is 4. The description correctly adds no parameter detail and instead spends its text on behavioral and return context, which is the right allocation.

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 makes clear this is a read-only descriptive/introspection tool: it 'states plainly what submit_enquiry does' and returns recipients, consent wording, and confirmation mechanics. It distinguishes itself from siblings (enquiry_fields supplies the form fields, submit_enquiry performs the action) by framing itself as the 'read first' explainer. It is slightly indirect in that it describes a sibling's behavior rather than naming its own verb+resource up front.

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 sequences this tool ahead of submit_enquiry, which is a genuine when-to-use signal. It does not spell out a when-not case or name alternatives, but the ordering guidance is concrete and actionable.

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