invoices_preview_estimate_template

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

The description adds no behavioral detail beyond the action itself. While annotations cover safety (readOnlyHint, destructiveHint), the description does not disclose what 'preview' produces (e.g., rendered content, a URL, a file) or any side effects. It merely restates the name, adding minimal value.

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 brief ('Preview Estimate Template'), which is concise but lacks structured detail. It is a noun phrase rather than a full sentence, and while it wastes no words, it also provides no context, making it more under-specified than efficiently concise.

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 tool with no output schema, the description should explain what the preview returns or how it is presented. It does not, leaving the agent uncertain about the result format. Given the tool's simplicity and existing annotations, additional context about the preview output would be expected but is absent.

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 input schema fully documents all three parameters (templateId, altId, altType) with descriptions and defaults, so schema coverage is 100%. The description adds nothing about parameters, but the baseline of 3 applies because the schema adequately handles parameter meaning.

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 clear verb ('Preview') and resource ('Estimate Template'), which conveys the core action. It is distinct from sibling tools like invoices_create_estimate_template or invoices_list_estimate_templates, but it does not explicitly differentiate itself, relying on the verb 'preview' to imply read-only behavior.

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?

No guidance is provided on when to use this tool versus alternatives such as listing or creating estimate templates. There is no mention of use cases, prerequisites, or conditions that would lead an agent to select this tool, leaving the agent to infer from the name alone.

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