list_csm_products

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds no behavioral context beyond that—no mention of pagination, default limits, or return shape. It fails to leverage the opportunity to describe what the tool does with the query/limit parameters or how it behaves on empty results.

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 sentence with no filler, front-loaded with the action 'List' and the resource. It is appropriately brief for a straightforward list tool.

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 list tool with no output schema and optional parameters well-documented in the schema, the description is nearly sufficient. It misses a note about what the output contains (e.g., product codes, descriptions) and the effect of the limit parameter, but overall it is complete enough for a basic 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?

Schema description coverage is 100% with both limit and query having their own descriptions. The description adds no additional parameter meaning, but since the schema fully covers parameters, the baseline of 3 applies.

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 the tool's action and resource: 'List products and services available in the CSM catalog.' It uses a specific verb and resource, but does not explicitly distinguish from sibling tools like list_catalog_items, so it misses full sibling differentiation.

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 a use case (when you want to see CSM catalog products/services) but provides no explicit guidance on when to prefer this over alternatives or any exclusions. It lacks contextual keywords like 'use for' or 'instead of'.

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