calculate_garden_soil

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

With no annotations, the description must disclose behavioral aspects. It only states 'Returns m³ and bag count', but does not explain how bag count is derived (requires bag volume input, which is not in schema), nor any side effects, authority needs, or performance characteristics.

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 concise (two sentences) but contains inaccuracies (bag volume input mismatch) and lacks clear structure. It front-loads purpose but then misstates inputs.

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 an output schema exists, the description does not need to detail return values, but it should still clarify the calculation method and bag volume dependency. The reference to 'list_bundles' is helpful but insufficient for an agent to decide usage among many sibling tools.

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 100% with brief descriptions, but the description introduces 'bag volume' as an input that does not appear in the schema, causing confusion. It adds no meaningful context beyond the schema and misleads about expected parameters.

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 'Compute soil volume (m³) and number of bags needed for a garden bed', which is a clear action on a specific resource. However, it mentions 'Inputs: area, depth, bag volume' but the schema includes length, width, and depth, not area or bag volume, causing potential confusion. Also, it does not differentiate from similar sibling tools like 'calculate_raised_bed_soil'.

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' and references 'list_bundles' for related calculators, but provides no explicit guidance on when to use this tool versus alternatives. It does not specify prerequisites, limitations, or exclusions.

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