stock_price_js

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description does not need to repeat safety. It adds the data source URL and return type (pandas.DataFrame), but does not disclose output shape or scope, which is a minor gap.

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 and includes structured param/return docstrings, but repeats the same phrase '美股目标价 or 港股目标价' twice. The URL adds context but could be trimmed without loss of essential meaning.

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 only states the return is a DataFrame of US/HK target prices, but does not explain columns, row scope, or how to filter for a specific stock. The singular optional parameter (symbol=us/hk) suggests market-level results, but this is not clarified, leaving a significant gap in completeness.

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 0%, but the description explicitly documents the parameter: ':param symbol: choice of {"us", "hk"}' and type str. This fully compensates for the lack of schema descriptions and clarifies the allowed values, which is critical for correct invocation.

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 identifies the tool as returning US or HK stock target prices (目标价), using '美股目标价 or 港股目标价' and a return type. It distinguishes from sibling spot-price tools like stock_us_spot and stock_hk_spot, but lacks an explicit action verb such as 'get' or 'list', making it slightly less direct.

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 no guidance on when to use this tool versus alternatives. It only specifies the parameter choices (us/hk) and return type, without exclusions, prerequisites, or references to similar tools. The URL is a source link, not usage context.

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