get_broker_setup_guide

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

Descriptions adds rich behavioral context beyond annotations: it details the guide's contents and enumerates supported brokers. Consistent with readOnlyHint and idempotentHint.

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?

Two sentences, front-loaded with key information. Every word adds value—no redundancy or fluff.

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?

Covers the tool's purpose, outputs, and parameters adequately for a simple retrieval tool. No output schema, but description makes return value expectations clear.

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?

Only parameter 'broker' has no schema description, but the description lists the enum values in text. Doesn't elaborate on the parameter's meaning or constraints beyond that list.

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?

Clearly states it gets a step-by-step setup guide for specific brokers, listing exactly what's included (env vars, credentials, paper trading instructions, rate limits, risk warnings). Distinguishes from sibling tools like connect_broker or validate_broker_connection.

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?

Implies usage when setting up a broker, but no explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or prerequisites.

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