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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds useful context about the return states (authenticated:true vs. connect_url) but does not disclose details like whether it makes network calls or how it determines provider connection status. With annotations covering the safety aspects, a 3 is appropriate.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. It is concise and well-structured.

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 no parameters, no output schema, and annotations cover safety, the description is fairly complete. It explains the two possible return states and what they mean. It could be slightly more explicit about the exact structure of the response (e.g., fields like authenticated, pending, connect_url) but overall it is adequate for a status-checking 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 tool has zero parameters, and schema description coverage is 100% (vacuously). The description explains the output semantics (authenticated:true and empty pending[] vs. connect_url and per-install URLs), which is valuable since there is no output schema. This compensates for the lack of parameters.

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 returns connection status and URLs, and explains the two possible states (all connected vs. missing credentials). It distinguishes itself from siblings like authenticate and show_version by focusing on status/URLs rather than performing authentication or showing version info.

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 implies when to use it (to check connection status and get URLs when credentials are missing) but does not explicitly state when not to use it or mention alternatives. It provides context about the two states but lacks explicit guidance on when to prefer this over authenticate or other tools.

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