connect_exchange

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

With no annotations, the description carries full behavioral burden. It discloses browser interaction and key security (keys never enter chat). However, it omits prerequisites (e.g., logged-in session), side effects (record creation), and post-action behavior (success message or error).

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 purpose, no redundant words. Each sentence provides distinct value: first states action, second adds behavioral and security context.

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 zero parameters, no output schema, and no annotations, the description covers the essential flow. Missing post-connection behavior (e.g., success, next steps) but overall adequate for a simple interactive tool.

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?

Input schema has no parameters (100% coverage). The description adds meaning beyond schema by explaining the process (browser page for key entry) and security guarantee. Since no parameters exist, description compensates well.

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 the tool connects a new exchange account via browser for entering API keys. It distinguishes from siblings like authenticate (user auth) and create_paper_exchange (paper trading) by specifying 'exchange account' and 'via browser'.

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?

No explicit guidance on when to use this tool vs alternatives like authenticate or create_paper_exchange. The description implies connection of a real exchange, but no prerequisites, conditions, or exclusion criteria are provided.

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