listServices

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

No annotations are provided, so the description carries full burden for behavioral disclosure. The description only states 'List services' with no information about whether this is a read-only operation, pagination behavior, authentication requirements, rate limits, or what happens when filters are applied. It lacks any behavioral context beyond the basic action.

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?

While technically concise with 'List services', the structure is poor because it includes extensive parameter and response sections that provide no value (all marked 'No description'). The front-loaded purpose is under-specified, and the bulk of the text is wasted space that doesn't help the agent.

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 15 parameters with 0% schema coverage, no annotations, and sibling tools that suggest this is part of a service management system, the description is severely incomplete. While an output schema exists (mentioned in context signals), the description doesn't explain what 'services' are, filtering logic, pagination behavior, or relationship to other tools. It fails to provide necessary context for effective use.

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% (no parameter descriptions in schema), and the description explicitly states 'No description' for all 15 parameters. The description adds zero semantic meaning beyond what's already in the bare schema types. With 15 undocumented parameters, this is a critical gap.

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 'List services' which is a tautology of the tool name 'listServices'. It doesn't specify what type of services are being listed, what resource is being accessed, or how this differs from sibling tools like 'listAlerts', 'listTeams', or 'listWorkflows'. The purpose is minimally stated but lacks differentiation and specificity.

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 absolutely no guidance on when to use this tool versus alternatives. The description doesn't mention any prerequisites, context for usage, or comparison to sibling tools like 'search_incidents_paginated' or other list tools. It provides zero usage context.

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