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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. Description adds that results contain canonical URLs and never access customer data, which is useful context beyond annotations.

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?

Two sentences with no fluff, front-loading the discovery purpose and adding a key behavioral fact (no customer data). Highly efficient.

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 read-only listing tool with output schema present, annotations already cover safety, and description states the primary use case. No critical missing info for an agent 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?

Schema has 0% description coverage, but descriptions of parameters are not provided. However, parameter names and constraints (limit, query, category) are self-explanatory, and the description's mention of 'discover' implies filtering capability. Baseline 3 is appropriate since the description does not add meaning beyond schema constraints.

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 specific verb (list) and resource (public calculators), with a clear purpose for discovery before choosing one. Distinguishes from siblings like run_public_calculator and get_public_calculator_contract.

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?

Explicitly frames when to use: discover free public calculators before selecting one. Does not explicitly state when not to use, but context and sibling names imply alternatives for specific calculators (e.g., calc_* tools).

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