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

With no annotations, the description carries the full burden and does well: it explicitly discloses that nothing is bought, ordered or paid, that no quote is guaranteed, and that the service is free — exactly the kind of commitment-boundary context an agent needs. It also previews the returned content (recipients, consent wording, confirmation step), adding transparency beyond a bare label.

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 as an imperative, followed by a dense but purposeful sentence covering the outcome and return contents. It is efficiently sized, though the second sentence is long and could be split for scanability.

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 parameterless informational tool with no output schema, the description sufficiently covers what the tool conveys and what it returns (recipients, consent wording, confirmation method). Nothing essential to correct invocation appears to be missing.

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 zero parameters, so per the rubric the baseline is 4. There is nothing for the description to clarify on the input side, and it correctly does not invent parameter detail.

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 the tool's function as explaining what an enquiry does on PPC agency Bristol — an information/description tool rather than a transaction. It is distinguishable from submit_enquiry (which acts) and enquiry_fields (which enumerates inputs), though the phrasing 'states plainly what submit_enquiry does' describes a sibling's behavior rather than naming the tool's own output directly.

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 'Read first' is an implicit sequencing instruction telling the agent to consult this before submitting, which is genuine usage guidance. However, it never names enquiry_fields or submit_enquiry as alternatives or states when this tool is unnecessary, leaving the routing to inference.

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