Get Catalogs

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description does not need to disclose safety. The description adds valuable behavioral details: pagination (page and per_page), pagination metadata, and the API endpoint. This extra context justifies a score above baseline.

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 four sentences, which is reasonably concise. However, the second sentence about fetching a specific catalog is misleading and unnecessary, detracting from conciseness. The rest of the description is well-structured, but the overall impact is average.

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 lack of an output schema, the description adequately explains the response format (pagination, JSON array, metadata). It also includes API reference and required parameters. The only shortcoming is the inaccurate claim about fetching a specific record, which slightly undermines completeness.

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%, meaning each parameter already has a description. The description merely reiterates that page and per_page control pagination and that company_id is required, adding no new meaning beyond the schema. 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 states 'Returns all Cost Catalogs,' clearly indicating a listing operation. However, the phrase 'fetch the full details of a specific Cost Catalog records by its identifier' is contradictory and misleading because the input schema does not include a catalog identifier parameter. This ambiguity lowers the score slightly.

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 lacks explicit guidance on when to use this tool versus alternatives (e.g., create_catalog, update_catalog). The confusing mention of fetching a specific record without a corresponding parameter may mislead the agent. No when-not-to-use or alternative tool references are provided.

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