get_all_a_share_quotes

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

Annotations already include readOnlyHint=true and openWorldHint=true, so the safe-read behavior is covered. The description adds useful context beyond annotations: built-in concurrency control and a caution about the large data volume, which helps the agent understand operational characteristics.

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 one concise sentence with a clear important marker and a necessary warning. It is front-loaded with the core purpose and includes no filler. Every phrase contributes meaningful information.

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?

For a tool with no output schema, the description covers key operational aspects: scope, filters, concurrency control, and data-size caution. It does not detail the return format or pagination, but the purpose is straightforward and annotations provide safety context, leaving minimal ambiguity.

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% for all three parameters, so the schema already documents each parameter well. The description adds a summary-level mention of market filtering and concurrency control, but does not provide additional semantic detail beyond the schema. Baseline 3 is appropriate.

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 the tool gets real-time quotes for the entire A-share market (5000+ stocks), using the specific verb '获取' (get) with an explicit resource scope. It distinguishes itself from sibling tools like get_a_share_quotes by emphasizing '全市场' (full market) and the filtering options.

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 provides clear context: it's for full-market real-time quotes, with market filtering and concurrency control. It also warns about large data volume. However, it does not explicitly mention alternatives or when not to use it, so it falls short of a 5.

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