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

Annotations already set readOnlyHint to true, so the description does not need to explain safety. It adds value by disclosing the return contents (identity and plan), providing helpful behavioral context beyond the annotations. No conflicting or missing critical behavior is apparent for this simple tool.

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 short sentences, front-loaded with the core action and then the return value. Every word earns its place; there is no redundancy or unnecessary detail.

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?

This is a low-complexity tool with no parameters, a read-only annotation, and no output schema. The description covers the purpose and the high-level return values, which is sufficient for an agent to invoke it correctly. Slight improvement could specify the output structure, but the minimal context makes this 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, so the input schema is trivially complete (100% coverage). Per the baseline guidance, a 0-parameter tool scores 4 without needing parameter descriptions. The description mentions no parameters, which is appropriate since none exist.

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 ('verify') and resource ('connection'), and clearly states what it returns (authenticated account identity and plan). This distinguishes it from sibling tools like estimate_capacity, generate_report, and pack_containers, which serve different purposes.

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 this tool is used to check the validity of the connection/authentication, which is a distinct and unambiguous purpose. While it does not explicitly mention when not to use it or name alternatives, its role as a verification tool is clear and siblings are unrelated, so the guidance is adequate.

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