get_stock_quote

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

With no annotations, the description must fully disclose behavioral traits. It states the tool returns 'real-time' data, which implies a read operation, but does not explicitly confirm it is safe (no side effects) or mention any rate limits, authentication needs, or error conditions. The disclosure is insufficient for a tool that likely interacts with an external API.

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 well-structured docstring with Args and Returns sections. It is concise (few sentences) yet informative, with no redundant or irrelevant content. Every sentence adds value, and the structure aids quick parsing by an AI agent.

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 low complexity (single parameter, no output schema, no siblings), the description is partially complete. It clearly defines the purpose and parameter, but lacks usage guidance and behavioral transparency. For a minimal viable description, it meets the basics but has clear gaps that could be filled.

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?

Despite 0% schema coverage, the description adds substantial meaning to the only parameter: 'symbol: Stock ticker symbol (e.g., AAPL, MSFT, GOOGL)'. It clearly explains the domain and provides examples. This compensates well for the lack of schema descriptions.

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 a symbol'. The verb 'Get' and resource 'stock quote' are specific, and the scope is defined. Since there are no sibling tools, no differentiation is needed. The description is direct and unambiguous.

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 no guidance on when to use this tool or when not to. There are no alternatives mentioned, and no context about prerequisites or limitations (e.g., which exchanges are supported). The agent receives no help in deciding whether to invoke this tool over hypothetical others.

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