calculate_raised_bed_soil

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

With no annotations, the description fully discloses outputs (soil m³, bag count, mix recommendation). It implies a read-only computation, but could explicitly state no side effects. No contradictions.

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 key information front-loaded: purpose, inputs, and outputs. Every sentence earns its place; no redundancy.

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 simple calculator with 3 parameters and described outputs (including mix ratios), the description is complete. It also references related tools via bundle, covering discovery needs.

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?

Parameter schema has 100% coverage, so baseline is 3. The description does not add new meaning to parameters beyond the schema; it only repeats input names and adds output context.

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 clearly states the tool computes soil volume for a raised garden bed, with a specific verb and resource. However, it does not explicitly differentiate from sibling tools like 'calculate_garden_soil' or 'calculate_compost_volume', though it mentions a related bundle.

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 says 'Use for gardening setup', providing clear when-to-use guidance. It also directs to sibling tools via 'See list_bundles', implying alternatives, but no explicit when-not-to-use or exclusion criteria.

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