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

Annotations (readOnlyHint=true, destructiveHint=false, idempotentHint=true) already indicate this is a safe, non-destructive operation. The description adds the behavioral detail that the tool returns a browser URL for credential setup, which implies it initiates an OAuth-like flow rather than directly performing the connection. It also includes a critical data accuracy contract that governs the agent's output behavior, which is valuable for correct invocation and response formatting.

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 moderately concise but includes a long data accuracy contract paragraph that is tangential to the tool's core purpose. While the contract is important for the agent's behavior, it is verbose and could be moved to a general instruction. However, the main functional description is front-loaded, and the contract is clearly separated. The length is justified by the need to enforce data accuracy rules, but it slightly reduces conciseness.

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 zero parameters, no output schema, and clear annotations, the description covers all essential aspects: what it does, when to use it, what it returns, and critical behavioral constraints. The data accuracy contract adds necessary guidance for the agent's response formatting. It is complete for a simple connector 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?

The input schema has zero parameters, so there is no schema burden. The description explains what the tool does without needing parameter documentation. The lack of params means the description's semantic content is sufficient. Baseline for 0 params is 4, and the description adds context about the output (browser URL) and the data accuracy contract, which is useful.

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 GunBroker seller account and specifies the output (a browser URL to open the credential setup form). It includes explicit trigger phrases ('connect GunBroker', 'set up GunBroker', 'link my GunBroker account') that distinguish it from sibling tools like get_gunbroker_connection_status or disconnect_gunbroker_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?

The description explicitly tells the agent when to use the tool: 'Use when the user says connect GunBroker, set up GunBroker, or link my GunBroker account.' This is a clear directive that guides selection.

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