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

Annotations already indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe read behavior is covered by annotations. The description adds useful detail about return values under different conditions (authenticated:true, empty pending[], connect_url), which is beyond annotations, but does not cover all potential side effects or rate limits. Thus, it adds moderate value.

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 compact two-sentence paragraph, front-loaded with the core purpose and then providing conditional outcomes. Every sentence adds value, with no redundancy or filler. This is exemplary 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, and simple annotations, the description is sufficient to understand the tool's behavior. It explains the two main states (all connected vs credentials missing) without needing to detail return formats. Slight deduction for not mentioning pagination or further error cases, but for a status check tool, this is complete enough.

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)Skip, so there is nothing for the description to explain. The schema coverage is 100% (empty properties), meaning no ambiguity. The description focuses on the return semantics, which is appropriate. Hence, a baseline of 4 is warranted.

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, distinguishing it from siblings like 'authenticate' and 'show_version'. It specifies the verb 'returns' and the resource (connection status), but does not explicitly contrast with all siblings, so a small deduction.

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 usage for checking connection status but does not explicitly state when to use it over alternatives like 'authenticate' or 'toolkit_info'. It provides no exclusions or alternative guidance, so it's adequate but not thorough.

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