stock_quote

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

No annotations are provided, so the description must cover behavioral traits. It states the return fields ('price, change, volume, market cap, P/E, sector, country, and more') and that it works for global stocks. However, it doesn't explicitly state that it is a read-only, non-destructive operation or mention any rate limits or authentication requirements.

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 well-structured: a brief intro, then bullet points for symbol formats, and examples. Every sentence adds value 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?

Given the tool's output schema exists (though not shown), the description lists all key return fields and covers global stock coverage sufficiently. It is complete for its purpose.

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 input schema has 0% description coverage for the 'symbol' parameter, but the description provides extensive detail on symbol formats with examples per region, adding significant meaning beyond the raw schema.

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's purpose: 'Get real-time stock quote for any global stock.' It specifies the action (get), the resource (stock quote), and the scope (global). This distinguishes it from siblings like nse_quote, bse_quote, and crypto_price.

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 examples for different regional formats (US, UK, Japan, Hong Kong, India) and mentions an alternative for Indian stocks ('use nse_quote for Indian stocks'). While it doesn't exhaustively list all alternatives, it gives clear usage context.

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