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

Annotations already cover read-only, idempotent, and non-destructive behavior. The description adds meaningful context beyond annotations by disclosing the OAuth scope requirement and the 'fulfilled orders' constraint, which are not present in the structured metadata. It does not contradict the 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?

The description is brief and front-loaded with the most critical information: 'Read-only' and the OAuth scope requirement. It avoids fluff and packs three useful pieces of info (read-only, auth, resource scope) into a single concise sentence, earning a solid score without being overly terse.

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 simple, single-optional-parameter read tool with no output schema, the description covers the essential context: the exact resource scope, auth requirement, and the presence of links in the response. It lacks details like pagination or sorting, but those are not critical for a tool this simple, and annotations cover safety.

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% (the only parameter, limit, is fully described). The description does not add any additional param-level semantics, so the baseline of 3 applies. No compensation needed.

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 resource ('trees of the signed-in user's fulfilled orders') and the access mode ('Read-only'), and the 'with a link to each tree in the forest' adds specificity. It is distinguishable from siblings like list_trees (which likely lists all trees) by scoping to the signed-in user's sponsored trees, though it does not explicitly name the alternative.

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 implies usage for a signed-in user's own sponsored trees and explicitly states the OAuth scope requirement, which serves as a precondition. However, it does not explicitly contrast with sibling tools (e.g., list_trees or get_forest) or state when not to use it, leaving the selection decision largely to inference.

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