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

With no annotations, the description carries the full burden. It discloses domain-level behavior of the enquiry flow (nothing is bought or paid, no quote guaranteed, it is free) and the consent/confirmation model, which is genuine context. It does not, however, state that this particular tool is side-effect free or 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?

"Read first" is properly front-loaded, but the body drifts into describing the sibling tool and carries SEO-style phrasing ("Digital marketing agency Swindon") that does not help an agent act. It is compact but not tightly focused on this tool.

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 informational tool with no output schema, the description does cover what the caller receives (recipients, consent wording, confirmation path) and the nature of the enquiry. Little is left ambiguous about the call itself, though the split of responsibility with enquiry_fields is unaddressed.

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 the baseline is 4; there is no parameter semantics to document. The description does not need to compensate for any schema gap here.

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 name and title signal a read/describe tool, and the description does say it "Also returns who receives the details, the consent wording, and how the person confirms." But most of the text describes what the sibling submit_enquiry does rather than what this tool returns, so the agent must infer that this is the informational counterpart to submit_enquiry.

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." gives an implicit ordering cue (call this before submit_enquiry), which is useful. However, it never explicitly says when to use this versus enquiry_fields, and there is no when-not guidance.

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