pdf_template_config_templates

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

No annotations provided, so the description carries the burden. The description discloses the purpose and mentions fields returned (slugs, names, descriptions, default colors) plus the intended downstream use. However, it doesn't disclose pagination, whether companyId changes the returned set, or any other behavioral details beyond listing. Acceptable but minimal.

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, both carry information — first states what the tool returns, second gives actionable guidance on using the result. No wasted words. Slightly front-loaded with the primary action.

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 list tool with one optional parameter and no output schema, the description adequately covers the purpose, return fields, and how the returned data connects to other tools (slug for updating config). The downstream guidance provides useful context for the config workflow.

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% — companyId is the only param and the schema already describes it as 'Company UUID (overrides configured default)'. The description doesn't add much about this parameter beyond what the schema already states, so baseline 3 is appropriate.

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?

Clear verb+resource: 'List all available PDF template designs' with specific fields (slugs, names, descriptions, default colors). Distinguishes from siblings pdf_template_config_get/update/preview which operate on the configuration, while this lists available template design options. Slightly less explicit on whether it's tied to a company or global.

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?

Some context is provided — says to use the slug when updating template configuration, which implicitly links to pdf_template_config_update. However, it doesn't explicitly state when not to use this tool or compare against the get/preview siblings, leaving the distinction mostly implied rather than stated.

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