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

With no annotations provided, the description carries full behavioral disclosure. It explains exactly what happens ('starts an enquiry with human providers who quote directly'), what does not happen ('nothing is bought, ordered or paid'), the cost ('it is free'), and what the tool returns: recipients, consent wording, and confirmation process.

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 compact and front-loaded with 'Read first.' The main sentence is dense but organized with semicolons, and there is little waste. Minor redundancy with the title's 'not a purchase, not a guaranteed quote' prevents a perfect score.

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, documentation-style tool with no output schema, the description is complete: it explains what the tool does, what submit_enquiry does, what is NOT involved, and exactly what information is returned (recipients, consent wording, confirmation method). An agent has enough context to call and interpret the result.

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 empty schema properties, so the schema provides no parameter semantics. The description appropriately focuses on the tool's output contents rather than parameters, which matches the baseline for a zero-parameter tool.

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-resource relationship: it 'states plainly what submit_enquiry does' rather than performing the enquiry. It clearly identifies the tool as a descriptive/educational tool and distinguishes it from the action-oriented sibling submit_enquiry by emphasizing 'nothing is bought, ordered or paid; no quote is guaranteed.'

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' gives explicit sequencing context: use this before acting on submit_enquiry. It also sets expectations about what the tool is not (a purchase or guaranteed quote), but it does not explicitly name alternatives like enquiry_fields or state when to prefer them.

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