get_fundamentals

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only hints at a limitation ('available issuer fundamentals', 'not a replacement'), but does not explicitly state whether the operation is read-only, what data is returned, or any side effects or prerequisites, which is insufficient for a tool without annotations.

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 with two clauses, every word earns its place, and the key information is front-loaded. No redundant filler or restating of the tool name.

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 tool's simplicity (one required parameter, no output schema, no annotations), the description is minimally viable but leaves ambiguity about what 'fundamentals' includes and what the return payload looks like. The caveat about full financial statements adds context but does not complete the picture for an agent invoking the tool.

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 description coverage is 0%, so the description must compensate. It clarifies that the tool works for 'one symbol', giving minimal cardinality context, but does not explain the expected format (e.g., ticker symbol), any constraints, or how the symbol parameter is used beyond that.

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 uses a specific verb ('Get') and resource ('Schwab's available issuer fundamentals') for one symbol, clearly distinguishing this from sibling tools like get_quotes or get_price_history. The added clause 'not a replacement for full financial statements' further clarifies its scope.

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 implies usage for fetching per-symbol fundamentals and explicitly warns it is not a substitute for full financial statements, but it does not name alternative tools or provide explicit when-to-use versus when-not-to-use guidance relative to siblings.

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