list_catalog_items

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly discloses the pagination trait — 'limit/offset paginate — this returns one bounded page, not the full table' — which is the key behavior for a list operation. However, it omits other meaningful behaviors, such as the fact that 'active' defaults to true (silently excluding inactive items) and the return format.

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?

Two short sentences with the core purpose front-loaded. The pagination sentence is nearly redundant ('limit/offset paginate' and 'returns one bounded page, not the full table' restate the same idea), but it is compact and wastes little.

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 5-parameter, no-annotation, no-output-schema tool, the description is thin. It explains pagination but not the filtering semantics (query, active, category) or the default filtering behavior. With no output schema, the absence of any return-format hint leaves the agent guessing at what fields a page contains.

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 low at 20% (only 'query' is documented in the schema), so the description must compensate. It adds meaning to limit/offset by explaining they paginate the result, but it contributes nothing for 'active' or 'category', which remain completely undocumented in both schema and description. Partial compensation only.

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 ('List service catalog items'), which clearly identifies the operation. The plural 'items' distinguishes it from sibling get_catalog_item, and the resource type separates it from list_catalog_categories or list_incidents. It doesn't explicitly name the alternative, but the purpose is unambiguous.

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?

There is no guidance on when to use this tool versus get_catalog_item, update_catalog_item, or the change/users listing siblings. The pagination note ('returns one bounded page, not the full table') describes behavior but does not address tool selection or exclusions. Usage context is only implied by the 'list' verb.

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