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

Annotations already declare readOnly, idempotent, non-destructive and open-world, and the description still adds substantial operational context: match semantics (best text match wins), quota behavior (first 5 successful reads per UTC day per network address are free and keyless), the auth mechanism (X-API-Key header after that), and the billing rule (0.04 credit only when an operation is returned). The no-charge failure modes are exactly the kind of behavior an agent cannot infer from structured fields.

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?

Purpose and return values are front-loaded, then usage, then pricing and auth, which is a sensible order. It runs long with the signup URL and repeats the private-network restriction (once as 'not charged', once as 'do not send'), costing a little tightness.

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?

There is no output schema, so the description correctly spells out return fields; both required parameters are covered; and the cost/auth/quota model an agent must know before calling is fully present. Nothing needed to call this tool correctly is 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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema by explaining that 'query' is a short intent matched against method/path/operation id/summary and that the best match is returned. That clarifies the expected granularity of the query string rather than merely restating the schema.

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?

States a specific verb and resource ('Read one operation from a public OpenAPI or Swagger JSON document, or from a simple YAML document') and then enumerates exactly what comes back (method, path, operation id, summary, required parameter and body fields). There is no ambiguity about what the tool does or what it produces.

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?

Gives concrete invocation guidance ('Send the document URL and a short intent, for example create a pet') and an explicit exclusion ('Do not send a URL on a private network'), plus conditions where no charge applies (private address, login wall, no match). It lacks an explicit statement of when to prefer this over some other approach, but with no sibling tools that gap is minor.

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