calculate_pyramid

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

With no annotations, the description alone must disclose behavior. It mentions outputs (volume, surface area) but fails to clarify that it expects 'base_length' (a side length) rather than 'base_area'. This mismatch could mislead an agent about input requirements.

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 brief (two sentences plus a line), which is acceptable. However, the content is structurally sound but factually flawed regarding inputs, reducing effectiveness.

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 tool's simplicity and an output schema (likely describing return values), the description adds some value (mentions surface area). But it fails to correctly describe the primary input, leaving a critical gap.

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 schema already describes parameters. The description adds 'base area' and 'optional slant' which are not in the schema, introducing confusion rather than clarifying meaning. This detracts from the schema's inherent clarity.

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 states it computes pyramid volume with a formula, but the input parameter is 'base_length' not 'base_area' as mentioned. This discrepancy undermines clarity. It does not sufficiently distinguish from many sibling geometry calculators.

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?

Only a vague reference to 'See list_bundles for related math calculators' is provided. No explicit guidance on when to use this tool versus alternatives, or any context-specific conditions.

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