healthcheck

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

Discloses behavior: calls auth.test per workspace, returns success/error, no retries, and meaning of failure. With no annotations, the description fully informs the agent of safety and failure modes.

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 front-load the purpose and then add necessary behavioral details. Every word serves a purpose—no waste.

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 zero parameters and presence of an output schema, the description fully covers the tool's operation, failure implications, and references external documentation (SETUP.md). Complete for a healthcheck.

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 exist (0 params, 100% schema coverage), so parameter semantics are not needed. Baseline 4 applies as description adds no redundant param detail.

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 uses specific verb 'Verify' and resource 'token validity per workspace', clearly distinguishing from sibling tools like list_workspaces or send_message. The purpose is immediately obvious.

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?

States 'Does not retry' and explains failure implies token invalidation, guiding when re-extraction is needed. While not explicitly listing when not to use, the context is sufficient given the tool's specificity.

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