manage_service_catalog

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

No annotations are provided, so the description carries the full burden. It does not disclose permissions, side effects (e.g., whether place_request creates a ticket or sends email), pagination behavior, or return values. The output schema exists, but the description adds no behavioral context beyond the arg list.

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 a compact docstring with a one-line overview and an Args list. It is well-structured and not bloated, though 'Service catalog operations' is a fragment and the list largely duplicates schema property names. The mapping of params to action values is useful and earns its place.

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 multi-action tool with 8 parameters and zero annotations, the description is incomplete. It lacks an overall purpose statement, per-action semantics (what each action does or returns), and any prerequisites or side effects. The parameter mapping is helpful, but the tool's behavior and integration with a service catalog are left unspecified.

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 0%, but the description's Args block adds meaning by mapping each parameter to the action(s) it applies to: ticket_id to get_requested_items, display_id/email/requested_for/quantity to place_request, and page/per_page to list_items. It also defines requested_for as 'Email of person for whom request is placed' and notes quantity default. This compensates for the missing schema descriptions, though it doesn't explain validation or formats.

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 opens with 'Service catalog operations,' which is vague and largely restates the tool name. The action values ('list_items', 'get_requested_items', 'place_request') clarify what the tool can do, but there is no explicit verb+resource statement or contrast with sibling manage_* tools.

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 guidance is given on when to use this tool versus managing tickets, changes, assets, etc. The action parameter lists supported operations but does not explain the scenarios for each action or exclude alternatives. Sibling tools like manage_ticket indicate the domain, but no explicit selection guidance is provided.

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