list-services

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

With no annotations provided, the description carries full burden but only states it 'gets' a list without disclosing behavioral traits like pagination (implied by limit/offset in schema), authentication needs, rate limits, or what format the list returns. It mentions nothing about whether this is a read-only operation or has side effects.

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 extremely concise with just four words, front-loaded with the core action. There's zero wasted language, though this brevity contributes to gaps in other dimensions.

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 a tool with 5 parameters (nested under 'query'), 0% schema description coverage, no annotations, and no output schema, the description is incomplete. It doesn't explain parameter usage, return format, or behavioral context, leaving significant gaps for an AI agent to understand how to use this tool effectively.

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%, so the description must compensate but adds no parameter information. The schema shows 5 nested parameters (app_id, limit, offset, name, types) under 'query', but the description doesn't explain any of them, their purposes, or how they affect the list retrieval.

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 'Get the list of services' states a clear verb ('Get') and resource ('services'), but it's vague about scope and doesn't distinguish from sibling tools like 'get-service' or 'list-apps'. It specifies what the tool does at a basic level without providing differentiation from alternatives.

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 description provides no guidance on when to use this tool versus alternatives like 'get-service' (for single service details) or 'list-apps' (for listing apps instead of services). There's no mention of prerequisites, context, or exclusions for usage.

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