detect_ytd_high_low

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

Annotations already indicate readOnly and idempotent. Description adds value by detailing cache behavior, data availability time, and comparison methodology. Does not contradict 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?

Well-structured with bullet points for examples and parameter list. Slightly verbose in some areas (e.g., 'All plans' at start could be integrated), but overall clear and 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?

Covers all needed context: plans, cache behavior, date constraint, sibling differentiation. With output schema existing, no need to explain return values. Complete for a 4-parameter tool with good annotations.

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, but the description thoroughly explains each parameter: date format and constraint, optional code, min_prior_sessions default and usage, detail flag. Fully compensates for schema gaps.

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 it screens for year-to-date high/low records. Specifies the verb 'screen' and the resource 'YTD high/low records'. Distinguishes from siblings like detect_ytd_high_low_range and detect_52w_high_low by naming them and explaining when to use each.

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 states when to use (for 年初来高値, 年初来安値, YTD high/low) and when not to (for multi-date scans use the range version, for 52-week use the other). Provides context about conventions and data availability.

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