list_services

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

With no annotations, the description carries the full burden. It mentions optional pagination and field filtering, but does not disclose that the tool is read-only, that it returns paginated results by default (limit defaults to 50), or any authentication or rate limit details. The phrase 'List all services' could be misinterpreted as returning everything at once.

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 two sentences, front-loading the purpose and then adding key features. Every word contributes value, with no redundancy or irrelevant information.

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 4-parameter list tool with no output schema, the description covers the essential purpose and features (pagination, field filtering). However, it omits details about default pagination behavior, ordering, or error handling. Given the simplicity of the tool, it is mostly complete but could be more explicit.

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%, so the baseline is 3. The description adds minimal value by noting field filtering reduces response size, but it does not clarify parameter relationships or provide additional context beyond the schema's own parameter descriptions.

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 clearly states the verb 'List' and the resource 'services', making the tool's purpose unambiguous. It also distinguishes from sibling tools like list_contacts or get_service by specifying 'services' and mentioning pagination and field filtering, which are unique to this tool.

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 implies usage for listing services via the verb 'List', but it does not explicitly state when to use this tool vs alternatives (e.g., get_service for a single service, or create_service for adding). No 'when not to use' or alternative tool references are provided.

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