calculate_compost_volume

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

No annotations exist, so description must disclose behavior. It mentions inputs and outputs, but inputs listed (household size, garden size) do not match schema (surface_m2, depth_cm). This inconsistency undermines transparency.

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?

Three sentences, concise but inaccurate. Includes misleading input list and omits depth_cm. Efficiency is lost due to incorrect information.

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?

Output schema exists and description mentions return values, but it does not cover all inputs (depth_cm missing) and adds phantom input (household size). Incomplete for a simple calculator.

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?

Description claims inputs 'household size' and 'garden size m²', but schema includes surface_m2 and depth_cm (with default). It adds incorrect information and omits depth_cm, failing to add meaning beyond schema and introducing errors.

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?

Description clearly states it computes compost volume from waste for bin sizing. Differentiates from many siblings by mentioning related 'jardinage' calculators. However, the mismatch with schema (household size not a parameter) slightly detracts.

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?

Says 'Use for compost bin sizing' which gives context. Points to list_bundles for related calculators, but does not explicitly exclude alternatives or provide clear when-not-to-use guidance.

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