saas_alerts_billing_list_dates

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety traits. The description adds valuable context about the 'authenticated partner' scope and the intended downstream use, which goes beyond the annotations. It does not describe edge cases like no dates available, but for a simple list operation this is sufficient.

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 short sentences, front-loaded with the action and scope, and immediately followed by usage guidance. No wasted words—every sentence earns its place.

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 the tool's simplicity (no parameters, no output schema), the description fully conveys what it returns (billing dates) and how to use them. The reference to the sibling tool provides the necessary context for chaining calls, making the description complete for an agent.

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?

The tool has zero parameters, and the schema is empty, so the description has no parameter burden. The description adds meaning by clarifying that the output is billing dates that can be fed into another tool, which helps the agent understand the data flow without needing parameter details.

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 'List all available billing dates for the authenticated partner' uses a specific verb (list) and clearly identifies the resource (billing dates) and scope (authenticated partner). It also distinguishes itself from sibling tools by pointing to saas_alerts_billing_get_details as the next step, making its role unambiguous.

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 explicitly states the primary usage pattern: 'Use the returned dates as input to saas_alerts_billing_get_details.' This tells the agent exactly when to use this tool and how it relates to a specific alternative, effectively guiding tool selection.

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