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

Annotations already provide strong behavioral hints: readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false. The description adds contextual behavior like what the return values mean (pending[] array, connect_url) and the conditional nature based on connection state. It doesn't contradict annotations. With annotations covering the safety profile, a 3 is appropriate as the description adds useful state-dependent 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?

The description is two sentences, both informative with no fluff. It front-loads the primary purpose and then details conditional behavior. Every clause earns its place. Excellent conciseness.

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, but strong annotations, the description is quite complete. It explains the key states (authenticated:true and empty pending[] vs. missing credentials returning URLs). It could potentially mention what pending[] contains or more details about the URLs, but for a simple status tool, this is adequate.

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, so the description does not need to explain parameter semantics. According to the rubric, 0 params = baseline 4. The description correctly focuses on return states rather than parameter details.

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's purpose: 'Returns connection status and URLs.' It uses a specific verb ('returns') and resource ('connection status and URLs'). While it doesn't explicitly differentiate from siblings, the context of sibling tools like 'authenticate' and 'toolkit_info' implies this is a status check tool, but the description could have been more explicit about its role vs. those.

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 to use the tool: 'When all providers are connected...' and 'When credentials are missing...'. It explains the return values in different states, giving the agent guidance on expected outcomes. It doesn't explicitly mention alternatives, but given the sibling tools, the usage scenarios are well-defined.

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