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

With no annotations, the description carries the transparency burden. It usefully discloses that the tool is free and requires no API key, and that it returns a real-time snapshot. But it doesn't mention potential limitations such as data delay, unsupported code formats, or behavior on invalid input. It's adequate for a simple read-only quote tool, but not comprehensive.

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 short, dense, and front-loaded with the core function before adding the use case and licensing note. Every clause contributes meaningful information with no redundancy.

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?

The tool is simple and has an output schema, so return-value explanation isn't needed. The description covers what the snapshot contains, when to use it, and the fact that no key is required. However, the missing parameter format guidance is a meaningful gap that could prevent an agent from invoking the tool correctly.

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 sole parameter `code` has zero schema description, and the tool description does not explain the expected format (e.g., 6-digit A-share code, HK ticker format, or prefix requirements). Since schema coverage is 0%, the description needed to compensate for this gap but does not.

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 provides a real-time quote snapshot for A-shares/HK stocks, listing specific fields (current price, open/high/low, turnover amount, turnover rate). It also gives a concrete user-intent trigger, making the tool's function easy to identify. However, it doesn't explicitly distinguish it from sibling tools such as ashare_kline or ashare_market_overview.

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 a clear usage condition: use when the user asks 'what price is a stock now'. This is practical and context-driven. It doesn't mention when not to use the tool or name alternative tools, so it falls short of full routing guidance.

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