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

Annotations declare readOnlyHint=true, so no contradiction; the description adds valuable behavioral context beyond that: 'Free, no payment, no auth required' and the exact return array structure. While it doesn't disclose rate limits or pagination, for a read-only list endpoint with a short fixed count (45), this is sufficient additional transparency.

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 three sentences but each serves a distinct purpose: what the tool lists, what it returns, and how to use it in the broader workflow. It is front-loaded with the main purpose and contains no filler or repetition of the tool name.

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?

Even without an output schema, the description explicitly states the return array shape, which is the key missing structured information. Combined with the read-only annotation and the explicit usage sequence involving sibling tools, the description is fully complete for a simple no-parameter list operation.

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 tool has zero parameters and the input schema is empty (100% schema description coverage), so the baseline for no parameters is 4. The description compensates by naming the returned fields ({ slug, name, description, icon, pageOptions, fonts, dataKeys }), which indirectly clarifies that no input is needed because the tool simply enumerates a fixed set.

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 opens with a specific verb and resource: 'List pdfzen's 45 public starter templates', enumerating example categories to make the scope concrete. It clearly distinguishes itself from sibling tools (get_starter, render_html_to_pdf, render_template_to_pdf) by focusing on listing available templates rather than fetching or rendering.

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?

Explicit when-to-use guidance is provided: 'Call this first to discover what fits the user request' and then a recommended sequence ('optionally call get_starter... then call render_template_to_pdf'). This directly addresses how to use the tool relative to its siblings, satisfying the highest bar for usage guidelines.

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