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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds value by disclosing the return behavior (a greeting that echoes the supplied note), which the annotations do not convey. It stops short of stating latency or error behavior, but the extra return context justifies a 4.

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?

Two short sentences, front-loaded with the tool's purpose and followed by the return behavior. No filler, no repetition of the tool title.

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 trivial health-check tool, the description plus rich annotations cover nearly everything an agent needs; the description even compensates for the absent output schema by describing the return. Only minor gaps remain (error/failure signaling), which are unlikely to affect correct invocation.

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?

Schema description coverage is 100% and the single 'note' parameter is fully documented in the schema, so the baseline is 3. The description's mention of 'the provided note' merely restates the schema and adds no format, range, or constraint detail beyond it.

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?

States a specific verb+resource (verify the FairWhere MCP server is reachable) and adds the return behavior (greeting echoing the note). It is unambiguous what the tool does, though it makes no effort to differentiate itself from siblings like fair_shortlist or open_plan_link.

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?

Usage is implied by the phrase 'verify ... reachable' and the connectivity-testing framing in the schema, but the description never says when to use this versus other tools or that it is a health-check-only utility with no side effects on real data. Adequate but leaves context to inference.

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