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

With no annotations, the description carries the full burden. It discloses the behavioral profile of the thing being described (nothing bought/ordered/paid, no guaranteed quote, it's free) and enumerates the returned content, which gives good context. However it says little about the tool's own behavior (that it is a side-effect-free read, has no auth/rate considerations, etc.), so it is adequate rather than rich.

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?

Three short sentences, front-loaded with the imperative 'Read first.' Most content earns its place, though the title's 'not a purchase, not a guaranteed quote' is partially restated in the body ('Nothing is bought, ordered or paid; no quote is guaranteed'), a minor redundancy.

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, no-output-schema info tool, the description tells the agent what it will get back (recipients, consent wording, confirmation flow) and what the described process entails, which is sufficient. It stops short of stating the return format explicitly, but the content is clear enough to call 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 input schema has zero parameters, so per the rubric the baseline is 4. There is nothing for the description to add or clarify on parameter semantics.

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 conveys that this read-only tool states plainly what submit_enquiry does and returns the recipients, consent wording, and confirmation flow. The framing is a bit meta ('Read first. States plainly what submit_enquiry does'), describing the subject matter rather than the tool's own action, but an agent can still infer this returns an explainer of the enquiry process. It does not differentiate itself from the nearby sibling 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?

'Read first' is an explicit ordering instruction that tells the agent to consult this before acting, and the tool is contrasted with submit_enquiry (which starts the enquiry). No exclusions or alternative info-tools (e.g. enquiry_fields) are named, so it is clear context without full alternative routing.

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