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

Annotations already declare readOnlyHint=true tent and destructiveHint=false, so this is a safe read operation. The description adds useful behavioral details: it returns authenticated:true and empty pending[] when all connected, and provides connect_url when credentials missing. It also mentions per-install URLs. This goes beyond annotations without contradicting them.

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 main purpose, and every clause adds value. It avoids redundancy and is appropriately concise for a simple tool.

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 is simple (no params, no output schema) and annotations are rich, the description fully explains the tool's behavior. It could mention that this is a status check only, but the readOnlyHint already implies that. It's complete enough for an agent to use effectively.

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 parametersnew, and schema coverage is 100%, so the baseline is 4. The description adds no parameter information because there are none, but it compensates by explaining the response behavior, which is relevant to interpreting the result. Since there are no params to document, the high baseline is appropriate.

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, which is a specific resource and purpose. It distinguishes from siblings like authenticate (which likely initiates connection) and report_bug, but doesn't explicitly mention those alternatives. However, the purpose is clear and non-tautological.

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 context on when to use this tool (to check connection status) by describing two states (all connected vs. missing credentials). It implies it's for diagnostics. It doesn't explicitly state when not to use it or mention alternatives, but the context is clear enough for an agent to decide.

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