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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description goes further and discloses the return channel per format — HTML as text, PDF as base64 specifically to avoid binary corruption in MCP clients — which is real behavioral value not present in 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?

Two sentences, zero filler, and the most decision-relevant fact (what is produced and from what) is front-loaded before the return-format detail.

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 correctly compensates by explaining how each format is returned. Combined with the schema covering all params, an agent has enough to call it, though error cases (invalid run_id, oversized reports) are unaddressed.

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%, so all four parameters (including the enum on format and the required project_id/run_id) are already documented in the schema. The description only echoes the format-to-encoding behavior, so the baseline 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?

Specific verb (generate/export) plus concrete resource (standalone HTML or PDF report) and source object (saved, project-attributed persona review). This clearly separates it from siblings like run_persona_review, run_persona_consensus, and render_mobile_audit_report.

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?

Establishes the prerequisite implicitly by requiring a 'saved, project-attributed' review and pointing at run_persona_review via the run_id description, so an agent knows it must run a review first. It stops short of explicit when-not-to-use or naming alternative export paths, so no exclusion guidance.

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