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

Annotations are minimal (all-false hints: not read-only, not destructive, closed-world), and the description adds the output format (PDF/PNG) and printability, which is consistent with a file-generation tool. The genuinely valuable behavioral disclosures — template is a no-op, unknown enum values silently fall back, issuerName empty hides the WHOLE issuer block, invalid orientation renders landscape — live in the schema descriptions, not the description. No contradiction with 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?

The core description is one efficient, scannable sentence with the resource and output formats front-loaded. The 'Certificate Generator —' prefix is redundant with the tool name and title, and the '[category: generate]' suffix adds marginal value, but there is no bloat or repetition beyond that.

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 10-parameter tool with no output schema, the description alone is thin, but the schema descriptions are so thorough that invocation is well-supported: every enum has fallback documentation, every dependency is spelled out, and the required field is flagged with a naming caution. The gaps are tool-selection context and explicit return semantics (file versus link/path), which neither the description nor an output schema covers.

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 the baseline is 3 per the rubric. The schema descriptions are exemplary: they document defaults, silent fallbacks ('Any other value silently returns the PDF'), field-name gotchas ('Field name is "certTitle" — not "title"'), and conditional rendering (issuerTitle only when issuerName is set). The description itself contributes zero parameter semantics, but the schema fully compensates.

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 verb and resource: 'Generate a printable certificate of achievement or completion as PDF or PNG.' This clearly distinguishes it from most generate_* siblings (barcode, invoice, QR code, etc.). However, the 'Certificate Generator —' prefix merely restates the tool name/title, and the differentiation from sibling document generators like generate_business_card or generate_invoice is implicit rather than explicit.

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 use case is implied by the wording 'certificate of achievement or completion' — an agent can infer it's for issuing formal certificates. But the description offers no explicit when-to-use guidance, no exclusions, and no routing to alternatives such as generate_invoice or generate_business_card for other document types. Tool-selection context is left entirely to inference.

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