任意ティッカーの現在値取得

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It clearly states what data is returned (current price, day change, sparkline) and the data source (Yahoo Finance). While it does not detail rate limits or data freshness, the scope is well-communicated. A slightly higher score would require additional context about response format or update frequency.

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 concise and front-loaded: three sentences deliver purpose, usage guidance, and a disclaimer. Every sentence serves a clear function, with no redundancy or unnecessary detail.

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?

Despite having no output schema, the description adequately covers what the tool returns (current price, day change, sparkline). Combined with the sibling context and single parameter, the description is complete enough for an agent to understand and use 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 schema already provides a detailed description of the symbol parameter, including examples and format. The description adds no extra meaning beyond what the schema offers. Since schema coverage is 100%, a baseline score of 3 is appropriate without additional compensation.

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 resource: current price, day change, and sparkline for any Yahoo Finance ticker. It explicitly distinguishes itself from the sibling get_market_snapshot by specifying that it handles tickers outside the 9 indicators covered by that tool.

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 explicit guidance on when to use this tool: for checking indicators other than those covered by get_market_snapshot. It also includes a disclaimer about not being investment advice, setting appropriate expectations.

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