BinanceMyAllocations

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get,' implying a read operation, but does not mention pagination, response size, rate limits, or what data is actually returned. This is minimal at best.

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, front-loaded sentence with no wasted words, making it very concise. However, it is arguably too terse for a tool with 6 parameters and a niche domain like SOR allocations, so it loses a point for balance.

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 has no output schema, no annotations, and a specialized subject (SOR allocations), the description is far too sparse to provide sufficient context. It does not explain what SOR allocations are, how to interpret results, or when to use the filters.

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 provides descriptions for all 6 parameters (100% coverage), so the description correctly does not repeat them. However, it adds no additional semantic context about how parameters like allocationId or fromAllocationId interact or when to use them, so baseline 3 applies.

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 a specific resource 'SOR allocations for Self-Trade Prevention,' clearly stating the tool's function. However, it does not differentiate this tool from closely related siblings like BinanceMyPreventedMatches or BinanceMyTrades.

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?

No guidance is provided on when to use this tool versus alternatives, nor are there any prerequisites or context for when SOR allocations would be needed. The description simply states what it does, not when to invoke it.

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