list_price_forms

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

No annotations are provided, so the description carries the full burden. The '[tier: readonly-owner]' tag signals a read-only operation, which adds some transparency. However, it doesn't clarify whether all price forms are returned or if there's any filtering, pagination, or ownership scope implied by 'owner'.

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 compact sentences: one stating the purpose and one mapping to the API endpoint plus tier. Zero wasted words, well front-loaded.

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 zero-parameter list tool with no output schema, the description is reasonably complete. It states the resource, purpose, API mapping, and read-only tier. Could benefit from noting whether all templates are returned or if any default filtering applies, but this is a minor gap for a simple 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 takes zero parameters and schema coverage is 100% (nothing to document). The description clarifies the resource type and usage purpose beyond the name alone. With 0 params, the baseline is 4, and the description meets this by explaining what the returned templates are used for.

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 (List) + resource (price book form templates) + purpose (build estimates and invoices). The 'Maps to GET /price_forms' clarifies the API endpoint. It distinguishes somewhat from siblings by specifying these are templates for estimates/invoices, though many sibling tools also list resources.

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 implies use when needing form templates for estimate/invoice building, which gives context. However, it doesn't explicitly state when NOT to use it or name alternatives among the many sibling list tools. The tier tag ([tier: readonly-owner]) implies a read-only context but no exclusions are given.

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