stocks_get_quote

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

With no annotations, the description must fully disclose behavior. It states a read operation but omits critical details: how the stock is determined (no parameters), what 'current' means (timezone, delay), and whether it requires prior setup. The lack of parameter explanation creates ambiguity.

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 a single, front-loaded sentence with no extraneous words. It efficiently conveys the core purpose without 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?

Despite the tool's simplicity (no parameters, no output schema), the description fails to explain what stock it returns or how 'current' is defined. The notable lack of parameters compared to typical stock quote tools is not addressed, leaving the agent confused about usage context.

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 zero parameters with 100% coverage, so the description has no obligation to explain parameter details. However, it could have clarified that no parameters are needed, earning a 4 (baseline).

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 retrieves 'current stock price and market data', which is a specific verb+resource combination. It naturally distinguishes from sibling tools like 'stocks_get_chart' (chart data) and 'stocks_search_symbol' (symbol lookup).

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?

No guidance on when to use this tool versus alternatives. It does not mention when to use stocks_get_chart or stocks_search_symbol, nor does it provide context for the tool's scope (e.g., fixed stock vs. user-specified symbol).

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