notification_certificate_pdf_url_get

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

Annotations already indicate a safe read-only, idempotent operation. The description adds the behavioral requirement that the certificate must have been previously generated, providing useful context beyond the annotations, though it does not describe error cases or URL expiry.

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 extremely concise: two sentences, front-loaded with the purpose, followed by the prerequisite. No redundant information, and every word 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?

For a simple getter tool with a single parameter, strong annotations, and an output schema, the description covers purpose and dependency effectively. It is complete enough for an agent to understand when and how to use it without additional explanation.

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?

The schema fully documents reportId as a mandatory UUID, so the baseline is 3. The description adds the semantic provenance of the reportId from notification_certificate_generate, which clarifies where to obtain the value and adds meaningful context beyond the schema.

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 clearly states the tool's function: retrieving a download URL for a previously generated notification delivery certificate. It uses a specific verb and resource, and distinguishes itself from sibling tools like notification_certificate_generate and evidence_report_pdf_url_get.

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 explicitly mentions the prerequisite chain 'notification_certificate_generate → reportId', giving clear context that this tool should be called after generating a certificate. However, it does not explicitly mention alternatives or when not to use it, 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.