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

Despite annotations already covering read/safe/idempotent, the description adds substantial behavioral context: market-hours intraday tick vs out-of-hours closing-price fallback, and the batch-tolerance behavior (a bad symbol yields empty price fields rather than failing the call). It even documents the trailing not-found/ambiguous note and the retry path — genuinely useful beyond the structured fields.

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?

Front-loaded with the core purpose, then market-hours nuance, then return format, then edge-case handling. It is dense but every sentence carries distinct information; the batch-error sentence is long but justified by the non-obvious behavior it discloses.

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 no output schema, the description carries the return burden and does so: CSV format, one row per symbol, and the trailing note listing unresolved/ambiguous symbols. Combined with timing and error semantics, an agent has everything needed to call and interpret this 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 description coverage is 100%, so both `all` and `symbols` are already fully documented including mutual exclusion and typo-tolerance. The description restates the one-vs-all usage but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource ('Get a live price snapshot for CSE stocks') and names the exact fields returned (price, change, change%). It clearly reads as a current snapshot tool, distinguishing it from historical siblings like get_ohlc_data or get_chart.

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?

Explains the two usage modes ('one or more symbols, or every CSE stock at once') and gives the retry instruction for unresolved symbols. It stops short of explicitly naming sibling alternatives (e.g. get_ohlc_data for historical), so it is clear context without full exclusion guidance.

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