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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable operational context beyond annotations: 'Returns success immediately with no database calls' and 'Does not count toward your monthly searches.' It also clarifies that it validates authentication, which is not disclosed by annotations. This is a good enhancement of the annotation-only safety profile.

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 three sentences, each with a distinct purpose: purpose, usage guidance, and a side-effect note. It is front-loaded with the core function and contains zero fluff or repetition. Every word earns its place.

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?

For a simple health-check tool with zero parameters and no output schema, the description covers everything needed: what it does, when to use it, what it confirms, and its side-effect-free nature. The lack of an output schema is fine because the description explicitly states it returns success. This is fully complete for the tool's complexity.

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. The description correctly does not mention any parameters. Per the baseline for zero-parameter tools, a score of 4 is appropriate since there is nothing to add semantically.

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 'Verify MCP server connectivity' and specifies that it 'Returns success immediately with no database calls.' This distinguishes it from all sibling tools that perform data operations, making it instantly clear when this tool is the relevant one.

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 gives direct usage guidance: 'Use this FIRST if experiencing tool errors' and explains what a successful response confirms (server reachable, authentication valid). It does not explicitly state when not to use it, but the 'FIRST' directive effectively communicates priority, which is strong guidance despite lacking exclusions.

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