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

With no annotations, the description carries the full burden and does so well: it discloses the semantic contract (nothing is bought, ordered or paid; no quote guaranteed; free) and clarifies this is a human-mediated process. It stops short of describing response format or latency, but for a zero-parameter read tool this is unusually rich 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?

Front-loaded with "Read first." followed by tightly packed clauses that each carry information about what the tool says and returns. Slightly dense in the middle, but no filler sentences.

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?

With no output schema, the description compensates by stating what comes back: who receives the details, the consent wording, and how the person confirms. Combined with the no-purchase/no-quote/free framing, an agent has enough to call and interpret it, though it omits any note on response timing or format.

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 there is nothing for the description to disambiguate; baseline 4 applies. The description correctly describes the nature of the returned content rather than inventing inputs.

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 names a specific verb (describes/states plainly) and resource (the enquiry flow behind submit_enquiry), and its title explicitly frames the output as an ENQUIRY with a human, not a purchase or quote. It is clearly distinguishable from submit_enquiry, the action it documents, though it does not name that sibling outright as an alternative.

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 explicit ordering guidance relative to submit_enquiry, which is the key usage decision for a describe tool. It does not spell out when NOT to call it or name alternatives by name, so it stops short of full when/when-not guidance.

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