queryBrokerAllUidDetails

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

Annotations already mark the tool as read-only and open-world, and the description adds meaningful behavioral context: the 1 req/sec throttle, the exchange broker/master-account eligibility, and the rule that accounts never configured via Set Rate Limit are omitted and use defaults. No contradiction with 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 purpose is stated in the first sentence, followed by a concise rate-limit line and two focused rules. Every section provides necessary operational context with no filler or redundancy.

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?

The description covers eligibility, throttling, and response membership, which is important. However, with no output schema and no parameter documentation, it omits response shape, pagination behavior, and the meaning of uids. This is adequate for a default no-arg call but incomplete for advanced use.

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%, and the description does not explain uids, limit, or cursor. The parameter names and schema constraints give some hints, but the agent must infer pagination semantics and what uids accepts, which is a significant gap.

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 states a specific verb and resource: querying all UID-level rate limits for master and subaccounts using the master account. This clearly distinguishes the tool from sibling tools like queryBrokerAccountInfo and queryBrokerEarning by focusing on rate-limit retrieval.

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 call context: it must be used with the master account, only exchange broker accounts can call it, and there is a 1 req/sec rate limit. It does not explicitly name alternatives or say when not to use it, but the scope and eligibility are clear.

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