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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful context beyond them: the output is a PNG rather than JSON, the visual contents of the card are enumerated, and the fallback relationship to widget rendering is explained. It omits auth/permission or rate-limit details, which keeps it short of 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?

Two sentences, zero waste, and the core purpose plus the fallback rationale are front-loaded ahead of the render_blockpage preference note. Every clause earns its place.

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?

There is no output schema, but the description compensates by describing exactly what the returned image depicts (username, human/agent badge, purpose, Tip / View-page buttons), which is what an agent needs to decide whether the PNG output is sufficient. Complete for a one-parameter render tool.

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% and the single parameter is documented with an example, so the schema does the heavy lifting. The description references the username only as a rendered element, not as input syntax, adding no meaning beyond the schema. 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?

States a specific verb and resource ('Render the blockpage preview card as a PNG image') and immediately distinguishes itself from the sibling render_blockpage by naming it. An agent can tell the two apart without opening either schema.

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?

Gives an explicit when-to-use condition (headless agents, CLI tools, raw HTTP – clients that cannot render MCP Apps widgets) and an explicit alternative with its selecting condition ('Prefer render_blockpage in clients with widget support'). Nothing is left to inference.

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