detect_distribution_days

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true. Description adds 'cache-only, no API call' explaining data source and performance characteristics. No contradictions with 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?

Concise and well-structured: purpose in first sentence, usage in second, plan support and args in subsequent lines. Front-loaded with no extraneous text.

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?

All parameters explained, purpose and usage covered, plan restrictions stated, and output schema exists (not shown but hinted). No gaps in context given the tool's complexity.

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%, but description compensates fully with detailed parameter explanations including defaults and IBD conventions for date, sigma_multiplier, window_sessions, and min_dist_days.

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?

Explicitly states the tool counts TOPIX distribution days in a rolling window, specifying the resource (TOPIX distribution days) and action (count). It distinguishes from sibling 'detect_follow_through_day' by referencing IBD method and noting 'See also detect_follow_through_day'.

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 guidance: use for institutional selling and market under distribution queries, check before confirming a follow-through day, and notes threshold (≥4 days in 25 sessions = failing uptrend). Clearly references an alternative tool (detect_follow_through_day).

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