list_services

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

With no annotations provided, the description carries the full burden. It discloses the search parameter's case-insensitive substring behavior, but does not mention pagination, result limits, ordering, or whether it returns only service names or additional metadata. This is a gap for a list operation.

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 succinct: a one-sentence purpose and a clearly formatted args block. Every piece of text adds value, with no redundancy or fluff.

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 simple tool with one optional parameter and an output schema, the description is reasonably complete. It covers the core purpose and parameter semantics, and the output schema handles return values. However, it does not address how this tool fits into the larger pricing API workflow, though that is not critical for basic 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%, but the description compensates by thoroughly explaining the only parameter 'search', including its optionality and case-insensitive substring matching. This adds meaningful value beyond the schema's type/default info.

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 tool's function: 'List available Azure services in the pricing API.' It uses a specific verb and resource, and is distinct from sibling tools like list_regions (regions) or search_prices (prices).

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 (when you need a list of Azure services) but provides no explicit guidance on when to prefer this tool over alternatives like search_prices or estimate_cost. It does not mention any exclusions or integration context.

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