Stock Price

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

The readOnlyHint annotation already signals a safe read, and the description adds useful return-content context: current price, bid/ask, and basic company stats. It does not contradict annotations, though it omits caveats like market hours, delayed quotes, or invalid-ticker behavior.

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, front-loaded, and organized with clear 'Use this tool when' and 'Returns' sections. The 'Args' line is slightly redundant with the schema, but the overall structure is clean and easy to scan.

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?

For a simple single-parameter read tool with no output schema, the description gives enough context: purpose, use cases, and a high-level summary of return values. It could be more detailed about exact output fields or data-source limitations, but it is sufficient for straightforward selection and invocation.

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 description provides only 'ticker: Stock symbol,' adding minimal meaning beyond the schema's string type and 'Ticker' title. With 0% schema description coverage, this is a small but not fully compensating clarification; examples or accepted formats would improve it.

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 uses a specific verb and resource: 'Get current stock price and company information,' and further clarifies that it returns price, bid/ask, and basic company stats. This clearly distinguishes it from the many options/volatility-oriented sibling tools.

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 explicitly lists when to use the tool: current stock price, bid/ask spread, and company information. It does not mention when not to use it or point to alternatives, but the listed use cases are clear and actionable.

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