get_equities_bars_minute

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

Annotations indicate read-only, idempotent, non-destructive. Description adds data retention (2 years) and plan dependency (Light with add-on). 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?

Concise with key info front-loaded. Minor redundancy in Japanese terms, but overall efficient for tool definition.

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?

With output schema present, description focuses on inputs and constraints. Covers parameter format and plan requirements. Could mention range query behavior, but sufficient for a bar data 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?

Schema has 0% description coverage. Description adds format (5-digit code, YYYYMMDD date), example for code, and distinction for 4-digit codes. Adds meaning beyond null strings.

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?

Specifically describes returning per-stock 1-minute OHLC bars, distinct from sibling tools like get_equities_bars_daily. Japanese term '分足株価' reinforces the minute-level focus.

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 lists use cases (minute-level price, intraday OHLC) and mentions data retention (2 years) and plan requirements. No explicit when-not-to-use or alternatives, but sibling differentiation is clear enough.

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