Intraday Line

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds context about data granularity and trade session options but does not disclose additional behavioral traits like rate limits, pagination, or date range constraints.

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?

The description is two sentences covering purpose, data granularity, and parameter behavior. No extraneous information; every part contributes meaning efficiently.

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 the description covers the core purpose and parameter, it does not specify the data's time scope (intraday presumably means current day only) or return fields. Without an output schema, the description leaves gaps about data structure and limitations, making it adequate but not fully complete.

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 100%, with both parameters described. The description adds value by explaining the default value for 'trade_sessions' ('intraday') and the meaning of 'all', which goes beyond the schema descriptions that only list the enum-like options.

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?

The description specifies getting intraday minute-by-minute price/volume data and explains the trade_sessions parameter. It clearly states the resource and action, but does not explicitly differentiate from sibling tools like 'candlesticks' or 'now'.

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?

The description implies usage for minute-level data but does not provide explicit guidance on when to use this tool versus alternatives such as 'candlesticks' for daily data or 'history_candlesticks_by_date' for historical periods. No when-not-to-use or alternative mentions.

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