analytics_range_accounts

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

Annotations already declare readOnlyHint=true and openWorldHint=true, indicating safe read operations with variable results. The description only restates the basic function ('account breakdown') without adding behavioral traits such as pagination, aggregation type, or authentication requirements. It is consistent with annotations, no contradiction.

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 short and front-loaded: three lines with the core purpose first, then usage guidance and trigger words. Every sentence adds value, though the trigger words could be placed separately. No unnecessary repetition.

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?

With three parameters, no output schema, and minimal annotations, the description should provide more context. It does not explain the output format, how paymentMethod affects results, or any edge cases (e.g., overlapping ranges). Incomplete for effective AI agent 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%, so the description must compensate. It mentions 'date range' implying startDate/endDate but does not describe their format or purpose, and completely omits the optional paymentMethod parameter. No details on regex patterns or constraints beyond the schema.

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 purpose: 'Get account breakdown for a date range.' It uses a specific verb and resource, and the name hints at range-based versus period-based siblings. However, it does not explicitly differentiate from the sibling analytics_period_accounts or other range tools (e.g., analytics_range_categories).

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 includes a 'When to use' section specifying account-level totals across a custom date range. However, it lacks guidance on when not to use this tool (e.g., for predefined periods or other breakdowns) and does not mention alternatives among the many sibling tools.

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