schwab_instrument

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

No annotations are provided, and the description does not disclose behavioral traits such as authentication requirements, rate limits, or the nature of the returned data (e.g., whether it's a snapshot or streaming). The description is minimal, leaving agents without crucial operational context.

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 very short and front-loaded with the core purpose. The Args section is included efficiently. No extraneous content exists, and every sentence serves a clear purpose.

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 and presence of an output schema, the description is adequate but not comprehensive. It omits what 'instrument information' includes (e.g., price, fundamentals, identifiers) and does not clarify when to use this over similar tools, limiting agent decision-making.

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 a single parameter 'symbol' with no description, but the tool description adds context by specifying 'Stock ticker symbol'. This provides basic semantics beyond the schema title, though it does not explain accepted formats or constraints.

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 instrument information for a symbol using a specific verb ('Get') and resource ('instrument information'). However, it does not differentiate from sibling tools like schwab_quote or schwab_search_instruments, which have overlapping purposes.

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 vs. alternatives (e.g., schwab_quote for price data, schwab_search_instruments for searching). It simply describes the action without contextualizing its use case.

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