list_recurring_services

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

Description lacks behavioral details such as pagination behavior, default ordering, filtering options, or any side effects. No annotations provided, so the description should cover these but does not.

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 very short but under-specifies critical details. Conciseness should not sacrifice clarity; here it does.

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 annotations and an output schema that is not described, the description is incomplete. It does not mention what the list contains (e.g., fields, pagination limits) or how to use pagination.

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 0%, and the description does not explain the page and page_size parameters. This is a significant gap; the agent cannot infer their purpose from the description alone.

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 lists recurring services, distinguishing it from sibling tools that list other entities. However, the term 'recurring services' could be more specific, e.g., service agreements or scheduled services.

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?

No guidance on when to use this tool versus other list tools. Sibling tools like 'list_services' or 'list_appointments' might overlap; description does not clarify exclusivity or context.

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