Health Check

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

The annotations already declare readOnlyHint=true and idempotentHint=true, establishing that this is a safe, read-only operation. The description adds value by specifying exactly what is verified (API token validity and connectivity), which goes beyond the annotations. No behavioral contradictions are present.

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 extremely concise, consisting of two short, purposeful sentences. It front-loads the core action and immediately provides a practical use case. There is no redundant or extraneous information.

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 the tool's simplicity (no parameters, no output schema), the description fully covers all necessary context. It clearly states what the tool does and when to use it, making it complete for an agent to select and invoke correctly. No gaps are apparent.

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 there is nothing to document in the description. The baseline for zero-parameter tools is 4, as the description need not compensate for missing schema coverage. The description's focus on the tool's purpose is appropriate.

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 uses a specific verb ('Verify') and clearly identifies the resource (API token and Cloudflare connection). This distinguishes it from all sibling tools, which focus on worker management, deployment, and domain operations. The statement is unambiguous and directly conveys the tool's function.

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 provides clear context for when to use the tool ('troubleshooting authentication issues'), which effectively signals the intended scenario. It does not explicitly name alternatives or when-not-to-use, but the unique purpose and sibling context make the usage clear without needing exclusions.

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