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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the 'canonical engine / Calculation Center Page 16700' claim, which is not actionable, and says nothing about validation failures for an unknown calculator_id or malformed inputs.

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?

A single front-loaded sentence with no padding. The 'same canonical engine as Calculation Center Page 16700' clause is the only questionable content, since it consumes space without helping the agent act.

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 tool with an untyped nested inputs object, no output schema, and no guidance on input shape or prerequisite discovery, the description is seriously incomplete. An agent could not construct a correct call from this definition alone.

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 0% with two required parameters, one of which is a free-form nested object. The description implies calculator_id is one of 32 choices but does not enumerate them or name the tool that does, and gives no hint about the structure of the inputs object, which is the parameter most likely to cause a failed call.

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: run one of 32 site calculators on the canonical engine. The purpose is clear, but it does not distinguish itself from siblings like list_calculators or get_calculator_spec, which an agent would need to call first, and the 'Page 16700' reference is opaque internal jargon.

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?

No when-to-use guidance and no stated prerequisites, even though the tool requires a valid calculator_id and a calculator-specific inputs object. It never points to list_calculators (to discover the 32 IDs) or get_calculator_spec (to learn the required input shape), which are present as siblings.

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