Broker connection setup & status

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

With no annotations provided, the description carries the behavioral burden. It discloses that it never reveals credential values, only whether they are set in the session, and that key guides are read-only. This is useful transparency, though it does not explicitly state whether the tool performs any network calls or has side effects.

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 two sentences with no filler. The first sentence front-loads all substantive content, and the second sentence gives precise invocation triggers. Every clause earns its place.

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?

For a zero-parameter informational tool with no output schema, the description is complete: it explains what is returned, what is deliberately not returned, and when to use it. An agent can decide to call this tool correctly without needing additional details.

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 tool has zero parameters and 100% schema coverage, so the baseline of 4 applies. The description adds no parameter-specific details because there are none to document; it correctly focuses on the tool's informational contents.

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 what the tool provides: an inventory of every connectable broker/exchange, the environment variables for credentials, whether they are set in the current session, and one-line key-creation guides. This distinguishes it from data-oriented siblings like broker_accounts, broker_positions, and broker_trades.

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?

It explicitly says when to call it: first when no broker data comes back, or when the user asks how to connect an account. It does not explicitly name sibling alternatives or state when not to use it, but the 'call this first' phrasing gives clear context.

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