setBrokerApiLimit

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

The annotations already indicate a mutating, non-destructive operation. The description adds meaningful behavioral context: a 1 req/sec endpoint rate limit, role-based authorization rules, and restrictions on which UIDs can appear. It does not describe reversibility or response behavior, but the added context goes beyond the annotations.

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 and well-structured: a purpose statement, a rate-limit note, and clearly bulleted rules. There is no filler, and the most important usage constraints are front-loaded.

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?

While the permission rules are helpful, the description omits essential details about the parameter structure and expected values. Since there is no output schema and the input schema has 0% description coverage, the agent is left without enough information to correctly call the tool or interpret results.

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 description coverage is 0%, so the description must compensate, but it only mentions the `uids` parameter. It does not explain the `list` wrapper, the required `bizType` enum values, or what `rate` represents in terms of units, range, or effect. An agent cannot reliably construct a valid request payload from the description alone.

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 opens with a specific verb and resource: 'Set API rate limit for specified UIDs under exchange broker account.' It clearly identifies the domain and action, and is distinguishable from sibling setters like setMmp or setPriceLimit.

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 gives explicit when-not conditions: only exchange broker accounts can call, master accounts can only target subaccounts and cannot set their own custom limit, and subaccounts can only target themselves. It does not explicitly name alternative tools, but the constraints are clear enough for an agent to decide whether it is permitted to use this tool.

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