robinhood_get_account_balance

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

No annotations present; description partially fills gap by listing returned fields, but does not disclose preconditions, side effects, or response structure. Since it's a read operation with no params, it's minimally adequate.

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?

Single sentence, no wasted words, front-loaded with verb and resource.

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 parameterless get-balance tool with no output schema, the description covers core purpose and return fields. Could mention return format or access requirements, but adequate.

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?

No parameters, so description cannot add param semantics. Baseline score of 4 applies as per rules.

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 it retrieves account balance and lists specific components (buying power, cash balance, total portfolio value), distinguishing it from sibling tools like get_portfolio or get_order_history.

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?

Implicitly clear when to use (when needing balance info), but lacks explicit guidance on when not to use or alternatives. Sibling tool names provide context.

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