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

No annotations are provided, so the description carries the full burden of disclosing behavior. It states 'Get the input schema' which implies a read-only operation, but it does not explicitly confirm safety, mention authentication requirements, side effects, or error conditions. The description adds minimal behavioral context beyond the action itself.

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?

The description is a single, focused sentence that is front-loaded with the verb and object. It contains no filler or redundant information, making it appropriately concise for a simple schema retrieval tool.

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?

Given the low complexity (one parameter, no output schema, no annotations), the description is adequate but not fully complete. It does not mention that the returned schema is in JSON format, how the calculator slug relates to list_calculators, or any prerequisites. Sibling tool names provide some context, but the description could offer more operational guidance.

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 input schema has one parameter 'calculator' with description 'Calculator slug', providing 100% schema description coverage. The description's phrase 'specific calculator' mirrors the parameter meaning without adding additional syntax, format, or source information. The baseline of 3 is appropriate since the schema already documents the parameter adequately.

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 uses a specific verb 'Get' and identifies the resource 'input schema' with a qualifier 'for a specific calculator'. This clearly distinguishes the tool from siblings like list_calculators (which lists calculators) and calculate (which performs calculations). The purpose is unambiguous.

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?

The description does not explicitly state when to use this tool versus alternatives. However, the purpose implies usage: one would fetch a calculator's schema before invoking it. No exclusions or alternative tool references are given, so it relies on the agent's inference from the sibling tool names.

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