queryBrokerAccountInfo

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

With no annotations provided, the description carries full burden. It mentions a rate limit and authentication requirement but does not disclose whether the operation is read-only, any side effects, or what the response contains. The agent is left uncertain about the tool's behavior.

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 with three sentences covering purpose, rate limit, and rule. It is well-structured and front-loaded with the core purpose. However, it could be more informative without becoming verbose.

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 parameters and no output schema, the description should provide more context about the returned information. It does not specify what 'account information' includes, leaving the agent to guess. The lack of disambiguation from sibling tools further reduces completeness.

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 has zero parameters with 100% coverage, so baseline is 3. The description adds no parameter information, which is acceptable since there are none. No value added but no deficiency.

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 the tool queries account information using a broker master account. It is clear and specific in terms of verb and resource. However, 'account information' is vague, and there is no differentiation from sibling tools like getAccountInfo or queryBrokerAllUidDetails, which could lead to confusion.

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 a precondition (requires exchange broker master account authentication) but does not offer guidance on when to use this tool versus alternatives. No exclusions or context for selecting this tool among many similar query tools.

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