get_stock_price

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

There are no annotations, so the description must disclose behavior. It states the tool returns price, bid/ask, and basic company stats, but the later 'Returns:' line says only 'Current price and company information,' creating an internal inconsistency. This ambiguity hurts reliability for an agent deciding what to expect.

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 has a clear structure with a summary, bullet list, and args/returns sections. However, it repeats the return value information in both the opening and the 'Returns:' line, making it slightly redundant. It's not overly long, but not as concise as it could be.

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 one-parameter tool, the description covers the essential purpose and when to use it. However, the return values are described inconsistently, and 'company information' is vague. With no output schema, the agent won't know the exact structure of the response, leaving a notable gap.

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%, so the description must compensate. It adds 'ticker: Stock symbol,' which provides some meaning but is minimal and doesn't include format examples, common symbols, or restrictions. This meets the baseline but leaves room for improvement.

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 opens with 'Get current stock price and company information,' clearly stating the verb and resource. It also lists specific use cases (current price, bid/ask, company info) that distinguish it from sibling tools focused on options, volatility, and other topics.

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 says 'Use this tool when the user asks about:' followed by a list, providing clear guidance on when to invoke the tool. It doesn't explain when not to use it or name alternatives, but the context is sufficient for a simple price-query tool.

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