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

The description adds meaningful behavioral context beyond the annotations: it documents the PDF MIME type, the state-dependent 404, and the 409 for unsupported openui dashboards. This is valuable because it warns the agent about preconditions and limitations that annotations alone do not convey.

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?

The description is two sentences with no filler. The primary purpose is front-loaded, and the second sentence efficiently delivers the only two error conditions an agent needs to know.

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 simple read-only rendering tool with annotations covering safety, the description is complete: it specifies the output format, important error states, and the prerequisite generation condition. The schema handles parameter constraints, so no critical information is missing.

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?

With 0% schema description coverage, the description needed to explain the parameters but does not mention artifactId or theme. The purpose makes artifactId inferable as the dashboard identifier, and the schema provides format constraints, but the description adds no direct parameter meaning.

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 action and resource ('Render a Duvo Pulse dashboard to a PDF document') and explicitly distinguishes the output type ('application/pdf, not JSON'), which differentiates it from sibling tools like getPulseDashboardHtml. The purpose is immediately clear and unambiguous.

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?

The description provides clear contextual conditions: the tool returns 404 until HTML has been produced and 409 for openui dashboards. This gives useful when/not-when guidance, though it does not explicitly name alternative tools for HTML or other output formats.

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