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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuine extra context: point-in-time semantics ('later ticket moves or deletion do not recapture the report'), an explicit error path for legacy reports, and the required 'tickets:read' scope. That is a meaningful behavioral addition beyond structured data.

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?

Four short sentences, information front-loaded with the core action first, then staleness semantics, then failure mode, then auth. Each sentence carries distinct information with minimal padding, though the phrasing is dense and jargon-heavy.

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 tool with no output schema and full annotation coverage, the description covers the key behaviors an agent needs: what it returns, staleness, error condition, and permission requirement. It only falls short on parameter documentation and any hint about how a snapshot_id is discovered.

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 0% and the description does not document snapshot_id at all: no format (UUID), no source (how to obtain it), no relationship to the 'owned project report' concept. The word 'owned' hints at an authorization constraint but the parameter itself is left entirely to the raw schema.

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 states a specific verb and resource: 'Verify and return the retained minimal inputs and regenerated counts of one owned project report.' This is far more informative than the tool name alone and implies a distinct scope from siblings like get_portfolio_snapshot or list_portfolio_snapshots. It does not, however, explicitly name an alternative tool to disambiguate.

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?

Usage is implied rather than stated: 'Reads stored inputs only' and the legacy-report fallback tell the agent what scenario this fits, but there is no explicit when-to-use versus when-not, nor any named sibling for the contrasting case. An agent can infer the context but must do some work.

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