analytics_range_payment_methods

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

Annotations specify readOnlyHint=true (safe read) and openWorldHint=true. The description adds no further behavioral details (e.g., output format, limits), leaving the agent uninformed about potential constraints or results structure.

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?

Three concise sentences front-load the purpose, usage, and trigger words. No redundant or extraneous content.

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?

No output schema exists, yet the description fails to specify what the 'breakdown' contains (e.g., list of payment methods with totals). Lacks coverage of account parameter behavior and range limits, making it incomplete for effective 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 has 0% description coverage. The description implies date range parameters but does not explicitly mention startDate, endDate, or the optional account parameter. Trigger words include 'range payment' but lack account context, leaving parameter semantics vague.

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 'Get payment method breakdown for a date range', identifying the resource (payment methods) and operation (breakdown). The trigger words help differentiate from period-based analytics tools, though it does not explicitly distinguish from other range tools.

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?

Provides a 'When to use' phrase for custom date ranges, offering basic context. However, it does not explicitly state when not to use or list alternative tools (e.g., analytics_period_payment_methods).

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