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

Annotations already establish readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds a useful disclosure of what is returned (connection state, username, AccessToken cache presence), but the remaining two paragraphs are generic output-formatting boilerplate unrelated to this tool's behavior.

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?

Only the opening sentence serves this tool; the attribution-footer and 'data accuracy contract' paragraphs are boilerplate about campaign budgets, ROAS, CPA and revenue that has no bearing on a credential-status check. Roughly two thirds of the text does not earn its place here.

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?

With no parameters, no output schema and full annotation coverage, the definition needs little more than the return-field summary it provides, so the core is adequate. It still omits the natural follow-up behavior (what to do when unconfigured, i.e. point at connect_gunbroker) and pads the remainder with irrelevant policy text.

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-level claims are made that could mislead.

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 first sentence names a specific verb and resource ('Check whether GunBroker credentials are configured for the current user') and even enumerates the returned fields (connection state, username, cached AccessToken). It is clearly distinguishable from write-oriented siblings such as connect_gunbroker and disconnect_gunbroker_connection, though it never explicitly contrasts itself with get_connector_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?

No when-to-use guidance is given: nothing says to call this before invoking GunBroker data tools, or that connect_gunbroker is the remedy when the status is disconnected. The agent must infer the routing from the name alone.

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