analytics_summaries_range

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

Annotations already provide readOnlyHint=true and openWorldHint=true. The description adds that the tool requires pre-checking periods, which hints at potential failures if periods are missing. It does not contradict annotations, and the behavioral disclosure is adequate given the annotation baseline.

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 concise, with a clear structure: purpose, precondition, usage guidance, and trigger words. Every sentence adds value without unnecessary verbosity. It is well front-loaded.

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 explains what the tool does, when to use it, and a necessary precondition. It does not detail what the summaries contain, but that may be domain knowledge. With many sibling tools, it effectively distinguishes itself. A small gap in parameter format prevents a perfect score.

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 input schema has two string params (startPeriod, endPeriod) with no schema description (0% coverage). The description implies they are period identifiers from analytics_periods_list, and mentions 'from period, to period' in trigger words, but does not specify format or acceptable values. This adds some meaning but not enough for full compensation.

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 it gets 'statement period summaries over an inclusive period range.' It explicitly differentiates from single-period tools like analytics_summary_by_period, saying 'Use for multiple statement periods or a span of months, not a single month total.' The trigger words also reinforce the scope.

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 explicit when-to-use: 'Use for multiple statement periods or a span of months, not a single month total.' Also gives a precondition: 'Before calling: Call analytics_periods_list first to confirm requested periods exist. If any period is missing, ask the user to choose from available periods.' This clearly guides correct invocation.

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