catalog_get_policies

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the result is a paginated list, which is useful behavioral context, but it does not describe return fields, pagination edge cases, or authentication requirements beyond what annotations already imply.

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 and front-loaded, stating the core operation first. It is slightly redundant because 'Returns a paginated list of pricing cards' largely restates the first line, and the endpoint duplicates the annotation title, but there is no bloat.

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 ten optional parameters, full schema description coverage, annotations covering safety, and no output schema, the description is largely complete for correct invocation. It could do more to explain the relationship with catalog_get_policy or what a pricing card contains, but the essentials are present.

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%, so all ten parameters are documented in the input schema. The description only mentions that results are paginated and does not add meaning beyond the schema for parameters like top, page, size, filter, search, or the expand flags.

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 a specific verb and resource: fetching all pricing cards for private-policy cloud, and adds that the response is a paginated list. This is clear enough to distinguish from most siblings, though the tool name 'catalog_get_policies' does not match the 'pricing cards' resource described and no sibling alternative is named.

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 gives no explicit guidance on when to use this tool versus alternatives such as catalog_get_policy or other catalog list tools. 'Fetch all pricing cards' implies a list operation, but there are no conditions, exclusions, or prerequisites to help an agent select this tool correctly.

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