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

Annotations already declare readOnlyHint:true and idempotentHint:true. The description goes beyond that by specifying the conditional response structure (authenticated:true with empty pending[], and connect_url when credentials are missing), adding behavioral context that is not present in the structured fields. No contradictions exist.

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 only two sentences, front-loads the core purpose ('Returns connection status and URLs'), and then adds conditional detail efficiently. Every word earns its place with no redundancy or filler.

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, read-only status tool, the description covers all realistic states (all connected vs missing credentials) and identifies key return fields (authenticated, pending, connect_url, per-install URLs). No output schema exists, so the description carries the responsibility, and it does so adequately for the tool's simplicity.

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 parameters, and the schema confirms no parameters are needed. According to the rubric, 0 params defaults to a baseline of 4. The description rightly omits parameter details, and the schema covers the lack of inputs completely.

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 uses a specific verb 'Returns' with a clear resource ('connection status and URLs') and explains two output conditions (all providers connected vs missing credentials), effectively distinguishing it from sibling tools like authenticate or marketplace.

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 provides clear context on when different outputs appear (when providers are connected vs when credentials are missing), implying appropriate use cases. However, it does not explicitly name alternative tools or state when not to use this tool, so it falls short of a 5.

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