Get catalog item list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds meaningful behavioral context beyond that by disclosing the price representation: prices are displayed as cents without a floating point, e.g., 17.99 becomes 1799. This is exactly the kind of format detail that prevents misinterpretation of returned data.

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 three short sentences, each earning its place: the first states the core function, the second gives a critical pricing-format detail, and the third provides usage context. Key information is front-loaded and there is no filler.

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 simple read-only list endpoint with two optional, fully documented parameters and no output schema, the description is largely complete. It explains what the tool returns, the pricing unit, and when to use it. It does not explicitly state default behavior when no filters are applied, but the name and schema make that reasonably inferable.

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%, and both parameters (name, category) already have clear descriptions in the schema. The tool description mentions pricing but does not add any extra meaning about the name wildcard or category enum values. With full schema coverage, a baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Retrieve catalog items available for order.' It clearly positions this as the catalog/index endpoint for orderable services and pricing, distinguishing it from billing operations like subscriptions or purchase orders. The final sentence reinforces the purpose as pre-order discovery of services and pricing.

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 explicitly states when to use this tool: 'Use this endpoint to view available services and pricing before placing orders.' This gives clear contextual guidance. It does not explicitly list alternatives or when-not-to-use conditions, but for a simple read-only list endpoint 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.