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

Goes well beyond the readOnly/idempotent/non-destructive annotations: it discloses the returned fields (filename, media_type, encoding, content, SHA-256), that PDF content is base64, that unsupported fonts or renderer dependencies produce an explicit error with an HTML fallback, and that tickets:read is required. That is rich behavioral context an agent cannot get from 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?

Front-loaded with the action and formats, then the return shape, then failure/no-share behavior and the auth requirement. Every sentence carries information, though the density is high and a couple of clauses could be tightened.

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?

With no output schema, the description compensates by describing the exact return fields and PDF encoding, and it covers error semantics, delivery scope, and required permission. An agent has everything needed to call and interpret the result.

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 coverage is 0%, so the description carries the burden, and it does characterize the format enum as 'JSON, CSV, accessible HTML or optional tagged PDF' — adding meaning (accessible HTML, tagged/optional PDF) beyond raw enum values. It implies snapshot_id is an owned saved report but does not restate the UUID/length constraint.

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?

Names a specific verb and resource ('Download one owned saved report') and enumerates the render formats, which distinguishes it from get_portfolio_snapshot (reads metadata) and create_portfolio_report_share (creates a link). The ownership scoping ('owned') further narrows what it acts on.

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?

States the context of use (download a saved report in a chosen renderer) and gives an explicit exclusion: 'No network delivery or share link is created,' which routes the agent to the share tools. It does not name the specific alternative tool, so it stops short of a 5.

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