stock_quote_by_id

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

No annotations provided, so description carries full burden. It indicates read-only behavior ('Gets stock quote'), but does not disclose additional traits such as rate limits, authentication requirements, or data freshness. Adequate for a simple read operation.

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?

Description is short and clear, but includes an 'Args' block that redundantly repeats the parameter name already in the schema. Could be more concise by omitting the redundant lines.

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?

The tool is simple with one parameter and an output schema exists, so description need not explain return values. However, it could briefly mention typical output fields (e.g., current price) to 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?

With 0% schema coverage, the parameter description 'Robinhood's internal instrument ID' adds essential meaning beyond the schema's just 'Instrument Id'. It clarifies the nature of the ID, fully compensating for schema gaps.

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?

Description clearly states 'Gets stock quote' with specific resource 'using Robinhood's internal instrument ID'. This distinguishes it from siblings that use symbols or other identifiers.

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 explicit guidance on when to use this tool versus alternatives like 'stock_price' or 'schwab_quote'. The description implies use when you have an internal instrument ID, but does not state alternatives or when not to use.

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