get_service_catalog_items

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

With no annotations, the description carries the full burden. It only states 'List all' and provides pagination args, but doesn't disclose read-only nature, potential large result sets, default pagination behavior, or ordering. Minimal transparency.

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?

Extremely concise with a clear Args block. Every sentence serves a purpose—the one-line purpose and two parameter definitions. No filler or redundancy.

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 pagination parameters, the description is acceptable but incomplete: it doesn't mention output format, ordering, or any usage constraints. The existence of an output schema is not leveraged to explain return structure, leaving some uncertainty.

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?

The schema has no descriptions (0% coverage), and the description barely compensates by restating 'Page number' and 'Results per page' which add little beyond the parameter names themselves. It doesn't explain defaults (though schema has defaults) or how pagination works together.

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 'List all service catalog items' with a specific verb and resource. It distinguishes itself from the sibling tool get_service_catalog_item (singular) by indicating it returns the full collection.

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?

No when-to-use or alternative tool guidance is provided. It doesn't mention that get_service_catalog_item should be used for a specific item or any context for when to use this list endpoint.

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