list_services

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

No annotations provided. Description implies a safe read operation ('list') and suggests no side effects. However, it does not mention pagination, rate limits, or any potential restrictions. Basic behavioral context is present but not rich.

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?

Two sentences, no superfluous words. Front-loaded with purpose and return information. Every sentence adds value.

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 no output schema, the description briefly states return fields. For a simple list tool, this is mostly sufficient. Minor gap: no mention of sorting or order, but acceptable for the complexity level.

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 coverage is 100%, so descriptions already document both parameters. The tool description adds 'Optionally filter by category' which mirrors the schema. No additional semantic value beyond what the schema provides.

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?

Description clearly states 'List AgentStorefront services' with specific verb+resource and mentions return fields (names, prices, descriptions). This differentiates it from siblings like get_service (single item) and search_services (search).

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 indicates optional filter by category but does not explicitly state when to use this tool versus alternatives like search_services. The context is clear enough for a simple list, but lacks when-not guidance.

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