list_services

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

No annotations provided, so description carries full burden. Discloses pagination (100 per page), search case-insensitivity, and tag filtering. Does not explicitly state read-only nature, but listing tools are implicitly read-only. Adequate transparency.

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?

Three short, focused sentences. Purpose is front-loaded. No redundant or extraneous content.

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 detailed schema descriptions and no output schema, the description covers purpose, use case, search/pagination behavior, and provides usage context. Could mention if any default tag behavior or link to full tag list, but overall complete for a simple list tool.

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 schema already documents each parameter. Description adds overall context and examples (e.g., 'stripe', 'amazon') but does not significantly augment semantic meaning beyond what is in the schema. Baseline 3 is appropriate.

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?

Clearly states it lists services with IDs and tags, and explicitly differentiates by noting its role in discovering service IDs for get_status. Distinct from siblings like get_status which retrieves status for a given service.

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?

Provides a clear use case ('discover service IDs for get_status') and describes search, tag filtering, and pagination behavior. Could be more explicit about when not to use, but context is sufficient for effective selection.

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