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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavior: it is free, never contacts a provider, pricing rules for fixed vs variable tools (provider price + 35%), and that unknown input schemas are flagged. That pricing and no-side-effect disclosure is real added value beyond the annotation block.

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 what is returned, then the pricing caveats and the cost/side-effect guarantees. Four short sentences, each carrying distinct information; only the billing-detail sentence could be trimmed without loss.

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 correctly enumerates the return payload (metadata, known parameters, pricing, request example) and discloses the free/no-provider-contact behavior an agent needs before deciding to call it. The only material omission is the format of the 'tool' argument.

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 description coverage is 0% for the single required 'tool' parameter, so the description carries the burden and largely fails: it never says whether 'tool' is an ID, a name, or a slug, nor what format or naming convention is expected. The mention of 'known parameters' refers to the returned metadata, not to the input parameter's 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?

States a specific verb (Read) and enumerates the resource precisely: local public tool metadata, known parameters, pricing metadata, and a JSON request example. The scope word 'local' plus 'does not contact a provider' implicitly separates it from run_tool, but no sibling is named explicitly, so differentiation is inferred rather than stated.

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?

Usage context is implied ('This is not an input-specific quote', 'Free; does not contact a provider') which signals a pre-flight inspection step rather than execution, but it never says when to prefer this over search_tools or get_run, nor states any prerequisites. Adequate but with clear gaps.

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