calculate_staircase

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

With no annotations, the description responsibly declares the return structure and the formula used. It sets expectations for the tool's output. It does not mention side effects, but as a calculator, this is sufficient behavioral disclosure.

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 very concise, with two front-loaded sentences that convey purpose, returns, and a pointer to related tools. No unnecessary words.

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 simplicity of the tool (one parameter, clear formula), the description is complete enough: it explains what it does, what it returns, and how to find related calculators. Missing an explicit statement of no side effects or units, but not critical.

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 already provides 100% coverage for the single parameter with a description. The description does not add new information about the parameter beyond naming the formula.

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 explicitly states 'Calculate staircase dimensions using Blondel formula' and lists the return fields, making the purpose clear. It also points to a related sibling (list_bundles) for similar tools, distinguishing itself.

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 implies usage for staircase calculations and directs to list_bundles for related calculators, offering some guidance. However, it does not explicitly state when not to use this tool or mention alternatives among the many sibling calculators.

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