detect_ytd_high_low_range

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

Beyond annotations (readOnlyHint, idempotentHint), discloses that it is 'cache-only, no API call' for supported plans and that setting code bypasses cache. No contradictions.

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?

Well-structured with purpose, guidelines, and parameter list. Minor redundancy (e.g., 'All plans.' repeated in supported plans). Front-loaded with key usage advice.

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 output schema existence, description covers purpose, parameters, behavioral traits, and plan support. Mentions detail parameter returns full data array. Complete for this tool.

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?

Despite 0% schema coverage, the description includes an 'Args' section that fully describes each parameter (format, default, effect like bypassing cache). Compensates completely.

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?

Clearly states 'Scan year-to-date high/low records across a date range.' Differentiates from sibling detect_ytd_high_low by advising use for multi-day queries instead of repeated calls.

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?

Explicit: 'Use this instead of repeated detect_ytd_high_low calls for multi-day queries.' Warns against splitting into parallel calls. Specifies date_from constraint and data availability time.

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