healthcheck

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

No annotations provided, so description carries full burden. Describes live GET, checks performed, and return value (ok=false with hint). Could be slightly more detailed on what 'token backend' and 'Graph reachability' entail, but overall adequate.

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 concise sentences in first paragraph, a clarifying second sentence in second paragraph. Front-loaded with purpose. Every sentence adds value. No unnecessary words.

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 no parameters, the description covers purpose, behavior, safety, and return format. Output schema exists (context indicates) but description mentions 'ok=false' hint, which covers expectations. Complete for this simple tool.

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?

No parameters in schema, so baseline 4. Description adds context about what the tool does (checks) beyond the empty schema, which is appropriate. No need for 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?

Description clearly states the tool verifies MCP configuration (accounts, token backend, Graph reachability). Specific verb 'verify' and resource 'MCP health'. Distinguishes from siblings which are for account management, posting, etc.

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?

Explicitly states it's safe to call anytime and never mutates. Provides clear context for when to use. Does not explicitly mention alternatives or when not to use, but given the sibling tools, it's implicitly clear.

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