stock_us_pink_spot_em

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

Annotations already declare the tool as read-only, idempotent, and non-destructive. The description adds the source URL and the return type (pandas.DataFrame), which is useful context. It does not contradict annotations and provides some behavioral information beyond the structured data.

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 exactly three lines, specifying the source, the return content, and the return type. Every sentence earns its place with no unnecessary information, making it highly concise and well-structured.

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?

Given the simplicity of the tool (no parameters, no output schema), the description covers the essential purpose, return type, and source. It could be improved by explicitly stating that it is for the pink sheet segment to avoid confusion with broader US stock tools, but it is still reasonably complete for a 0-parameter 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?

There are zero parameters, so the description does not need to add parameter semantics. The schema coverage is 100% vacuously, and the description appropriately includes no parameter information. This aligns with the baseline for no-parameter tools.

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 explicitly identifies the resource as '粉单市场实时行情' (pink sheet market real-time quotes) and provides the source URL from East Money, distinguishing it from sibling tools like stock_us_spot_em by specifying the pink sheet market segment. The verb is implicit but clear: it returns real-time quotes.

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 fetching pink sheet real-time quotes but does not provide explicit when-to-use or alternative guidance. It lacks exclusions or comparisons with sibling tools, so it is at the implied usage level.

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