Get requested items

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered without the description. The description adds only the scoping insight that results are per-ticket; it says nothing about ordering, empty-result behavior, or whether non-SR tickets return an error.

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?

One sentence with no filler, and the resource plus its scope are front-loaded. It could be tightened slightly for a more scannable structure, but nothing in it is wasted.

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 one-parameter, read-only list tool with an output schema and complete annotations, the description covers what to fetch and from where. The only meaningful gap is the absence of guidance on behavior for tickets with no requested items or non-service-request tickets.

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% and the single ticket_id parameter is documented with a helpful format note (#INC-123 / #SR-123). The description adds no further constraint on the parameter, so the baseline 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?

States a specific verb ('List') and a specific resource ('service catalog items requested on a service-request ticket'). The ticket-scoping clause distinguishes it from the catalog-listing siblings like list_service_items and search_service_items, though it never names those alternatives explicitly.

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 phrase 'on a service-request ticket' implies this is the follow-up to fetch items attached to an existing SR, which is useful implied context. But there is no explicit when-to-use guidance, no stated prerequisite (e.g. that the ticket must be a service request), and no named alternative for listing the catalog itself.

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