billing_getCatalogItemListV1

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

No annotations are provided, so the description carries full burden. It discloses that prices are in cents (e.g., 1799 for $17.99). This is a key behavioral detail beyond the schema. It does not mention other traits like caching or rate limits, but the primary behavioral aspect is covered.

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 short (three sentences) and front-loaded with the core purpose. Every sentence adds value: first sentence states the action, second clarifies pricing format, third suggests usage. No fluff.

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 there is no output schema and no annotations, the description adequately covers purpose, pricing detail, and usage context. It could mention pagination or limits, but for a simple catalog list tool, it is sufficiently complete.

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 coverage is 100%, so baseline is 3. The description adds value by explaining wildcard search for the 'name' parameter (e.g., '.COM*'). This goes beyond the schema description and helps the agent use parameters correctly.

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 clearly states 'Retrieve catalog items available for order.' It is a specific verb+resource, and the context of viewing services and pricing distinguishes it from sibling tools like billing_getPaymentMethodListV1 or billing_getSubscriptionListV1.

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 says 'Use this endpoint to view available services and pricing before placing orders.' This provides clear usage guidance. However, it does not explicitly mention when not to use it or alternatives, but given sibling tool names, the context is sufficient.

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