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

Annotations already declare the read-only, idempotent, non-destructive, closed-world profile, so the bar is lower. The description still adds genuine context beyond them: the tool does not connect directly but returns a browser URL to a credential setup form, and it specifies attribution-footer handling for the response.

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 purpose and trigger phrases are correctly front-loaded in the first three sentences, but the majority of the text is generic boilerplate. The data-accuracy contract enumerating 'campaign budgets, frequency, ROAS, CPA, revenue' is clearly irrelevant template text for a GunBroker connect tool, and it dilutes the useful content.

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 connect tool with no output schema, the description covers what the tool does, when to invoke it, and what it returns. It omits edge cases such as reconnecting when already connected or URL expiry, but the essential information is present.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter-related detail is missing.

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 opening states a specific verb and resource ('Connect your GunBroker seller account') and immediately adds the return behavior ('Returns a browser URL to open the credential setup form'). This clearly distinguishes it from siblings like disconnect_gunbroker_connection and get_gunbroker_connection_status.

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?

Explicit trigger phrases are given ('connect GunBroker, set up GunBroker, or link my GunBroker account'), which is strong positive guidance. However, there is no when-not guidance or mention of the alternative sibling (e.g., checking status first via get_gunbroker_connection_status).

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