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 declares this is a read operation, that nothing is bought/ordered/paid, that no quote is guaranteed, that it is free, and it enumerates what is returned (recipients, consent wording, confirmation). It does not describe any side effects or failure modes, but for a zero-param read tool this is solid disclosure.

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 body is a single tight sentence. There is mild redundancy in the near-synonym list "bought, ordered or paid," but it reads as deliberate emphasis on the non-transactional nature rather than filler.

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-param, no-output-schema describe tool, the description supplies the semantic context an agent needs: what the tool returns and what it is not. It is close to complete; only the relationship to enquiry_fields is absent.

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 beyond what an empty schema already conveys.

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 that this tool returns plain-language documentation of what submit_enquiry does, naming the specific resource (the enquiry flow on PPC agency Leeds). It clearly distinguishes itself from the write-side submit_enquiry, though it never mentions the sibling enquiry_fields, so sibling differentiation is only partial.

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 explicit sequencing cue relative to submit_enquiry, which is genuine when-to-use guidance. However, there is no mention of when not to use it or how it relates to enquiry_fields, leaving the alternative undocumented.

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