get_quote

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

No annotations are provided, so the description carries the behavioral burden. It clearly states the return fields (latest price, previous close, absolute/percentage change, currency) and the error payload for invalid or unreachable data. This is solid, though it does not address latency or data freshness.

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 front-loaded with a one-sentence summary and uses compact Args/Returns sections. Every sentence adds useful information with no tautology or filler.

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 quote tool with no output schema, the description is complete: it documents the parameter, the return contract, and failure behavior. Nothing an agent needs to invoke or interpret the call correctly is missing.

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 schema has no description coverage for the ticker parameter, so the description must compensate. It provides concrete ticker formats ('AAPL', 'MSFT', 'PETR4.SA') and notes B3-listed stocks, adding real value beyond the schema's bare 'Ticker' title.

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 a specific verb and resource: 'Get the current price and day change for a stock ticker.' This clearly distinguishes it from sibling tools like get_portfolio_metrics or get_historical_summary, which operate at portfolio or historical levels.

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 establishes that this is for single-ticker current quotes, but it does not explicitly say when-not-to-use it or point to alternatives like compare_assets or get_historical_summary. The ticker examples imply usage but do not provide exclusion criteria.

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