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

Given annotations already declare readOnlyHint=true and destructiveHint=false, the description adds extra context by explaining the response shape (authenticated:true, pending[], connect_url) and how it behaves when credentials are missingcars. It also implies the tool may provide per-install URLs, which is useful. No contradiction.

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 a single sentence that is moderately concise but includes some redundancy (e.g., 'when all providers are connected' and 'when credentials are missing' are somewhat redundant with 'pending[]'). It is front-loaded with the main action, but the sentence could be tightened without losing meaning.

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?

The tool is relatively simple with no parameters and no output schema, so the description covers the key behavioral aspects. However, it doesn't specify the exact format of URLs or how to handle partial connections (e.g., some providers connected, others not), which might be a gap for complete understanding.

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 has zero parameterscars, so the parameter semantic burden is minimal. The description clarifies the response semantics (like what authenticated and pending mean) even though it doesn't need to explain parameters. Since schema coverage is 100% (vacuously), baseline of 3 is set; the description adds value by explaining conditions, earning a 4.

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 it returns connection status and URLs, with specific details about behavior (authenticated:true, pending[], connect_url). While it distinguishes itself implicitly as a status/connect tool, it doesn't explicitly contrast with 'authenticate', but its purpose is clear and specific.

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 explains what happens in different conditions (all providers connected vs. missing credentials), which implicitly suggests when to use it—to check status or get connection URLs. However, it does not explicitly state when to use it versus alternatives like 'authenticate' or provide any exclusions, leaving room for confusion about when to call this versus initiating authentication.

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