calculate_garden_soil

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

No annotations are provided, so the description must disclose behavior. It does not explain how bag count is derived (e.g., assumed bag volume) or any assumptions made about the garden bed shape. The return is described briefly but insufficiently for a safe invocation.

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 with two sentences, but the second sentence contains inaccurate input information. The reference to list_bundles adds slight value.

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?

The tool has many siblings, and the description does not differentiate itself. The missing bag volume input parameter makes the tool ambiguous for precise use. Given the output schema exists, the return description is less critical, but the input inconsistency undermines completeness.

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 descriptions (length_m, width_m, depth_cm) are adequate, but the tool description incorrectly lists 'area, depth, bag volume' as inputs, contradicting the schema. This adds confusion rather than 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 soil volume and bag count, which is clear. However, it mentions inputs 'area, depth, bag volume' while the schema only has length, width, depth. This mismatch partially obscures the purpose.

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 it provides no guidance on when to use this tool over siblings like calculate_compost_volume or calculate_raised_bed_soil.

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