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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false. The description adds that it returns L/year and recommended bin volume, but an output schema exists and no auth, rate-limit, or other behavioral constraints are disclosed. It adds some context but not much beyond annotations and output schema.

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, front-loaded with the main purpose, then usage and related tools. The statement about return values is somewhat redundant because an output schema exists, but overall the text is tight.

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 low-complexity calculator with a complete input schema, output schema, and annotations, the description covers most needs. However, the inaccurate input list ('household size') reduces completeness and could confuse an agent about the actual required parameters.

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%, so baseline would be 3, but the description lists 'household size' as an input when no such parameter exists, and it omits the schema's depth_cm parameter. This actively misleads about the required inputs despite the schema being complete.

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?

States a specific verb and resource: computing compost volume from kitchen and garden waste over a year. The purpose is clear and distinguishes it from generic volume calculators in the sibling list.

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?

Explicitly says to use it for compost bin sizing and points to list_bundles for related 'jardinage' calculators. It gives clear context but does not state when not to use it or name a direct alternative.

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