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 well covered. The description reinforces this with 'Read-only' and lists the counters returned, but adds no deeper behavioral context such as freshness guarantees, performance implications, or limitations.

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?

The description is a single, dense sentence with the key 'Read-only' trait front-loaded. Every phrase adds information, and the list of counters is compact and scannable without unnecessary 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 zero required parameters and a fully documented schema, the description adequately conveys what data is returned. The absence of an output schema is compensated by the explicit list of counts, though subtle details like whether 'visitors' overlaps with the class breakdowns are left unspecified.

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 description covers 100% of the single optional 'fields' parameter, including its enum values and the omit-for-all behavior. The description merely echoes those counter names without adding new meaning, so the baseline of 3 applies.

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 clearly identifies the tool as returning statistical counts for forests, listing concrete metrics such as trees, groves, visitors, and traffic classes. The verb is implicit in 'Counts of...' and the resource is specific enough to distinguish it from generic get_forest, though it does not explicitly differentiate itself from sibling tools.

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?

No guidance is given about when to choose this tool over alternatives like get_forest or list_trees. The 'Read-only' prefix hints that it is for observation rather than mutation, but there is no explicit context, when-to-use, or mention of situations where another sibling would be preferable.

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