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

Annotations already cover the safety profile (readOnly/ idempotent/ non-destructive). The description adds real behavioral context beyond them: immutability ('Original reports and downloads never change'), the interpretation of empty results, and the pagination continuation mechanisms. It does not describe auth requirements beyond the 'tickets:read' scope note, keeping it from a 5.

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?

Five terse sentences, front-loaded with what is read and followed by caveats and pagination. Every sentence carries information; density is high but nothing is wasted.

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, annotated tool with no output schema, the description covers interpretation caveats, immutability, and pagination well enough to call correctly. The only gap is that return-shape details depend on the undefined cursor fields.

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%, so the description must carry parameter meaning. It explains continuation via next_before_relation_id (mapping to before_relation_id) and hints at an outgoing cursor, but never defines snapshot_id or limit. Partial compensation only, so a baseline-plus 3.

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?

States a specific verb (Read) and a specific resource (outgoing replacement chains and incoming owner declarations) scoped to one owned saved report. This distinguishes it from nearby siblings like get_portfolio_snapshot, list_portfolio_report_history, and supersede_portfolio_report. Slightly jargon-heavy ('owner declarations'), which keeps it from a 5.

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?

It clarifies semantics ('Absence means no replacement recorded, not approval'), which is genuinely useful guidance. However, it never states when to choose this tool over alternatives such as diff_portfolio_snapshots or list_portfolio_report_history, so usage is implied rather than explicit.

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