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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it succeeds. It clarifies that nothing is bought, ordered, or paid, that no quote is guaranteed, that the service is free, and that the tool returns details about recipients, consent wording, and confirmation process. This is rich, honest behavioral context.

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 filler, opens with the most important usage instruction ('Read first'), and packs the essential caveats and return-value highlights into a compact, readable block. Every sentence earns its 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 no-parameter, no-output-schema informational tool, the description is complete: it explains what the tool does, what it does not do, and what information it returns. There is no missing behavioral or usage context an agent would need to invoke it 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, so the baseline is 4. No parameter documentation is needed beyond the empty schema, and the description correctly focuses on behavior rather than filling a non-existent parameter gap.

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 verb—'States plainly what submit_enquiry does'—and names the exact resource, Machinery Transport Quotes. It clearly distinguishes itself from sibling tools: it is the explanatory read-first tool, not the action tool (submit_enquiry) or the field definitions tool (enquiry_fields).

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 instruction 'Read first' explicitly tells the agent to use this tool before taking an action, giving clear usage context. It does not explicitly enumerate when not to use it or compare with enquiry_fields, but the ordering guidance is sufficient for this low-complexity informational tool.

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