Health check

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

Discloses behavior beyond annotations: 'makes NO Weeek API call (no token required, no network)', explaining why it works even with a missing or expired token. This aligns with the readOnlyHint and idempotentHint annotations, adding useful context about auth and network independence.

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?

Three concise sentences: purpose, distinction from siblings, and usage guidance. All content is relevant and front-loaded, with no filler.

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?

The description fully covers the tool's behavior, usage context, and edge cases (missing token). The tool is simple, and the description is complete given the schema and annotations.

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 schema describes msg as 'Message to echo back', and the description adds how it appears in the output: 'returns pong: <msg>'. This enriches the parameter semantics without being verbose, exceeding the 100% schema coverage baseline.

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's purpose: 'PRIMARY tool for connection sanity-check: returns pong: <msg>'. It also distinguishes itself from siblings by explicitly stating it makes no Weeek API call, unlike weeek_get_me.

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?

Provides explicit guidance: 'Use when the agent first connects to verify the MCP transport itself is alive before reaching for any weeek_* tool.' Also contrasts with weeek_get_me, clarifying when not to use it.

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