get_current_stock_price

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

No annotations exist, so the description must carry the full burden. It does not disclose behavioral traits such as data freshness (real-time vs delayed), dependency on market hours, error handling for invalid symbols, or rate limits. The agent lacks critical context for usage decisions.

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 concise sentence that is front-loaded with the essential action and resource. However, it may be overly minimal, lacking details that could fit without clutter.

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 simple nature (one parameter, no output schema, no annotations), the description provides basic purpose but omits necessary context like whether the price is real-time, during market hours, or for any exchange. More context would improve completeness.

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 coverage is 100% with a description for the single parameter 'symbol'. The description adds no extra meaning beyond the schema (e.g., the example values are already in the schema). Baseline 3 is appropriate since the schema does the heavy lifting.

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 'Get the current stock price for a given symbol' clearly states the verb (get), resource (stock price), and scope (current, for a given symbol). It distinguishes itself from siblings like get_historical_stock_prices by specifying 'current'.

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 is provided on when to use this tool versus alternatives (e.g., get_stock_price_by_date). There are no prerequisites, exclusion criteria, or contextual hints about market hours or data freshness.

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