sc_cash_breakdown

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

No annotations are provided, so the description carries the full burden. It states the output components and that the response is 'compact,' but does not disclose whether data is real-time or cached, access prerequisites, rate limits, or side effects. Minimal but acceptable for a read-only tool.

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?

Two sentences effectively front-load the purpose and a usage tip. Every sentence earns its place with no superfluous content.

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?

An output schema exists, so return values are partially covered. The description lists the key fields (buying power, cash, credit, derivatives). However, the single parameter is not addressed, reducing completeness. With many sibling tools, the description provides enough context to distinguish this one.

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 one optional parameter (portfolio_id) with 0% schema description coverage. The description completely omits any mention of this parameter, failing to add meaning beyond the schema. It does not explain what the parameter does or its default behavior, leaving a gap for the agent.

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 'Get Scalable Capital cash breakdown' and lists specific components (buying power, available cash, credit, derivatives availability). This verb+resource combination is distinct and unambiguous among the sibling tools, none of which overlap with this function.

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 explicitly advises 'Use before placing orders to check available funds,' providing a clear use case. It does not mention when not to use or alternatives, but the context is sufficient for an AI agent to understand the primary scenario.

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