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

No annotations provided, so description carries full burden. It only states outputs (volume m³ and L) but lacks details on assumptions (e.g., average depth), limitations, or parameter dependencies (e.g., shape-specific inputs).

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 purpose, no filler. Every sentence adds 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?

Given output schema present and simple tool, description is adequate but misses behavioral context (e.g., parameter dependencies) that would be helpful for correct invocation.

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 parameter descriptions. The description adds 'Inputs: shape, dimensions' which is redundant. It does not clarify conditional logic (e.g., diameter_m only for round shape). Baseline 3 applies as schema covers basics.

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 'Compute swimming pool water volume in m³ and liters. Use for pool maintenance dosing.' It specifies the resource (swimming pool) and the action (compute volume), distinguishing it from sibling tools like calculate_aquarium_volume.

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?

Explicit use case 'Use for pool maintenance dosing' provides context. Mentions alternative 'See list_bundles for related 'vie-quotidienne' calculators' but does not explicitly state when not to use this tool.

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