invoices_list_estimate_templates

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds nothing beyond that—no mention of pagination, default behavior (e.g., defaults to GHL_LOCATION_ID), or what the response contains. It does not contradict the annotations, but it also does not enrich them.

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 a single short phrase with zero wasted words. It is front-loaded with the primary action. However, it is so minimal that it approaches under-specification; conciseness is not the issue, but the lack of content is. Still, for pure conciseness, it is efficient.

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?

Given that the tool has five parameters including pagination (limit/offset) and search, and no output schema exists, the description should mention important context such as default altId behavior, pagination semantics, or that it returns a list of templates. The description covers none of this, leaving agents without guidance on how to use the parameters effectively or what to expect.

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 all five parameters (altId, limit, offset, search, altType) are already documented in the schema. The description adds no parameter-level detail, so it relies entirely on the schema. Baseline of 3 is appropriate given full schema coverage.

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 'List Estimate Templates' states a clear verb and resource, but it is essentially the tool name repeated. It does not differentiate this tool from siblings like invoices_list_estimates (which lists estimates, not templates) or invoices_list_invoice_templates (which lists invoice templates). The purpose is clear but lacks specific scope or distinguishing details.

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 description provides no guidance on when to use this tool versus alternatives. There are many similar list tools (e.g., invoices_list_estimates, invoices_list_invoice_schedules), and no context is given about which one to choose. It does not mention any prerequisites, exclusions, or conditions.

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