get_quote_intraday_price

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

No annotations exist, and the description only states that it returns a DataFrame and mentions 'toon' format. It does not discuss data freshness, pagination behavior, rate limits, or what 'intraday' precisely means. Behavioral context is minimal.

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 fairly concise with a clear header and structured Args section. It front-loads the purpose. Minor verbosity in the Args list but still efficient.

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 4 parameters, no annotations, and no output schema, the description should provide richer context on pagination, time range, and return column structure. It fails to do so, leaving significant gaps for the agent.

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?

The description adds some meaning beyond the schema by noting 'max: 100000' for page_size and explaining 'toon' format. However, there is a mismatch: schema default for page_size is 100, but description says 500. This inconsistency harms reliability.

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 clearly states 'Get quote intraday price from stock market', specifying the verb and resource. However, it does not explicitly differentiate from sibling tools like get_quote_history_price or get_quote_price_depth, relying on the tool name for distinction.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks when/when-not instructions, which is a gap given many sibling tools for quotes.

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