get_balance_allowance

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read via 'retrieve' but never states whether authentication is required, whether the data is on-chain vs cached, or any rate/scope behavior. For a query tool with zero annotation coverage this is a notable gap.

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 Args block is well-structured, but the lead sentence is bloated with opaque modifiers ('functional', 'structural', 'metrics') and the token_id note is convoluted. It is appropriately sized overall but not as front-loaded or plain as it could be.

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 need not be explained. However, for a tool with no annotations and no sibling routing, the description omits authentication/scope context and any hint of when this beats get_positions, leaving meaningful gaps for proper invocation.

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 coverage is 0%, so the description is the only source of parameter meaning, and it delivers: it defines asset_type ('COLLATERAL' for USDC balance, 'CONDITIONAL' for outcome token holdings) and the conditional dependency of token_id. The wording ('Required intrinsically when... functions as') is awkward and the token_id format is unspecified, but it substantially compensates for the bare schema.

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 verb 'retrieve' is clear, but the resource is obscured by jargon: 'functional token balance and structural approval threshold metrics' is abstract where 'token balance and allowance' would be precise. An agent can infer this reports balances/allowances, but the phrasing is vague and gives no differentiation from siblings like get_positions.

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?

There is no statement of when to use this tool versus alternatives (e.g. get_positions, get_activity), nor any prerequisites or context. Usage must be entirely inferred from the name and the one-line purpose.

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