list_pricebook_equipment

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

No annotations exist, so the description must carry full behavioral disclosure. It fails to mention that the tool supports pagination (page, page_size) or filtering (active_only), nor does it describe any side effects or return characteristics. The description is a mere restatement of the tool's name.

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?

Extremely short but only because it is incomplete. It uses only 3 words, missing essential details. This is under-specification, not conciseness.

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 the tool has three parameters, an output schema, and many siblings, the description is severely lacking. It does not mention pagination, filtering, or the scope of results. An agent cannot determine what data it retrieves or how to use it effectively.

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 0%, meaning the input schema provides no descriptions for the three parameters. The tool description does not even list the parameters, let alone explain their meaning (page, page_size, active_only). It adds zero semantic value beyond the schema structure.

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 'List pricebook equipment' but is too vague to distinguish from many sibling tools like list_pricebook_materials or list_pricebook_services. It does not clarify what constitutes 'pricebook equipment' or how it differs from other pricebook listings.

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 usage guidelines provided. The description gives no context on when to use this tool versus alternatives, no prerequisites, and no hint of filtering or pagination usage.

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