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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond that: the 12-month sponsorship term, the returned price components, and the workflow note about calling it before stating a price.

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 short, purposeful sentences with the key behavioral fact front-loaded. Every sentence earns its place: what it returns, the fixed term, and when to call it.

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 single-parameter, read-only tool with robust annotations, this is complete. There is no output schema, but the description names the return components and currency unit, and the workflow note gives the agent enough to select and invoke the tool correctly.

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 fully documents the single quantity parameter, including range and volume discounts, so the baseline is 3. The description only echoes 'N trees' and adds the 12-month context, without providing new parameter-level details that the schema lacks.

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 names the exact deliverable: a final price quote for sponsoring N trees for 12 months, including unit price, total in euro cents, and discount. This is a specific verb+resource definition that clearly distinguishes it from siblings like get_design, get_forest, and get_order.

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?

'Call it before you tell the user a price' gives explicit, actionable guidance on when to invoke this tool. It does not name alternatives or exclusions, but no other sibling tool plausibly competes for this quoting purpose, so the context is clear.

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