setBrokerApiLimit

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

No annotations exist, so the description must disclose all behavioral traits. It mentions a rate limit of 1 req/sec and caller restrictions, but does not explain side effects (e.g., whether existing limits are overwritten), idempotency, or response structure. The behavioral disclosure is incomplete.

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 concise, front-loaded with the purpose, and uses bullet points for rules. It avoids unnecessary words but could be slightly more compact. Every sentence adds value.

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 complexity (nested array parameter, no output schema, no annotations), the description lacks completeness. It does not describe what the tool returns, whether the operation is atomic, or how to handle errors. The rules are helpful but not enough for full understanding.

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 must compensate. It mentions 'specified UIDs' and 'rate limit' at a high level but does not explain the structure of the 'list' parameter or the meaning of 'bizType' and 'rate' fields. Parameter details are insufficient for correct invocation.

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 action ('Set API rate limit') and the resource ('specified UIDs under exchange broker account'). It distinguishes itself from sibling tools like setLeverage or setAutoAddMargin by specifying the broker account context.

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 provides explicit rules for when to use this tool: only exchange broker accounts can call, and it explains master vs subaccount constraints. It does not mention alternatives or when not to use, but the rules are sufficient for basic guidance.

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