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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered and the description's 'Read-only' adds no new information. It does add 'bounded' and 'live forest' context, implying limited, current data, but it adds no further behavioral caveats such as freshness or performance. No contradiction with annotations.

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?

A single sentence that front-loads the read-only safety flag, then states the resource, the summary nature, the output categories, and the limit. No filler or redundant elaboration.

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 read-only tool with 0 required params, the description explains what the summary includes and the default/max limit, and the schema documents the bbox filter. It is slightly light on return-structure details, but acceptable for a summary tool with no output schema and rich annotations.

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 description coverage is 100%: bbox and limit both have clear descriptions. The description only repeats the default/max for limit and does not add new parameter semantics; baseline 3 is appropriate because the schema carries the full burden.

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 names the resource ('forest') and the operation ('Bounded summary') and lists concrete output dimensions (counts per tree type, growth stage, origin, grove levels, newest trees), so an agent can infer what the tool returns. It does not explicitly contrast it with sibling get_forest_stats, but the bounded-summary framing is a clear differentiator.

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 'Read-only' and 'Bounded summary' but gives no explicit when-to-use or when-not-to-use guidance. Sibling tools like get_forest_stats and list_trees exist, yet the description offers no routing or exclusions, so agents must infer the appropriate context from the name and output list.

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