Lists available PDF invoice template designs with slugs, names, descriptions, and default colors so you can choose the correct slug when updating template configuration.
List all available PDF template designs with their slugs, names, descriptions, and default colors. Use the slug value when updating the template configuration.
| Name | Required | Description | Default |
|---|---|---|---|
| companyId | No | Company UUID (overrides configured default) |
Changes observed during successful MCP inspections.
v1.0.17Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by disclosing the shape of the result (slugs, names, descriptions, default colors) and clarifying that slugs are the key consumed by the update tool. It does not say whether templates are global or per-company.
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 tight sentences with zero waste: the first front-loads what is listed and what fields come back, the second gives the actionable follow-up. No filler or restatement 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?
With no output schema, the description usefully enumerates the return fields and explains how the slug feeds the update tool, which is enough to call it correctly. The remaining gap is the scope of the listing (global vs company-scoped) and whether companyId changes the result set.
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% and there is only one optional parameter (companyId, with a documented override meaning), so the schema carries the semantics. The description never mentions the companyId override, adding nothing beyond the schema, which is the expected baseline here.
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?
States a specific verb and resource (list PDF template designs) and enumerates the returned fields (slugs, names, descriptions, default colors). It hints at its relationship to pdf_template_config_update by telling the agent to use the slug there, but never distinguishes itself from pdf_template_config_get or pdf_template_config_preview.
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 second sentence gives a downstream usage hint ('use the slug value when updating the template configuration'), which implies this is a discovery step before configuration. However, it never states when to call this instead of pdf_template_config_get or pdf_template_config_preview, and gives no preconditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.