analytics_period_outliers

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

Annotations already declare readOnlyHint=true and openWorldHint=true, providing safety and openness context. Description adds that it fetches 'largest transactions' but does not elaborate on ordering, pagination, or limits beyond schema. Adds some value but not substantial beyond annotations.

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?

Description is well-structured with clear sections (Before calling, When to use, Trigger words) and front-loaded key information. Length is appropriate, but could be slightly more concise by merging some phrases.

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?

While usage guidelines are solid, the description fails to explain parameter semantics and does not hint at the return structure (e.g., list of transactions with amounts, dates). With no output schema, this omission leaves the agent guessing about the tool's full behavior.

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 provides no explanation of the two parameters (period, limit) or their semantics. The agent must rely solely on the schema names and types, which lack descriptions, making parameter usage unclear.

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 largest transactions in a statement period', specifying verb, resource, and scope. It differentiates from sibling tools like analytics_range_outliers by focusing on a single period.

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?

Explicitly instructs to call analytics_periods_list first to confirm period existence, and advises asking user if missing. Provides 'When to use' context and trigger words, clearly delineating when to use this tool over alternatives.

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