Check setup

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

With no annotations, the description must carry behavioral disclosure. 'Verify' strongly implies a read-only diagnostic, and the listed items clarify scope, but the description does not explicitly confirm non-mutation, nor does it explain failure behavior or what happens if checks fail.

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 sentences with zero filler: the first states what the tool verifies, the second states when to use it. Every word earns its place, and the key information is front-loaded.

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 no-input diagnostic, the description provides enough to select and invoke it correctly: it names the checks performed and says to run it first. It does not describe the response shape, but the absence of an output schema and the simplicity of the call make this a minor gap rather than a blocking one.

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 sketchy so the schema is fully covered by its empty parameter list. The description adds no parameter details, and none are needed; baseline 4 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 identifies a specific verb ('Verify') and concrete resources: API key, connectivity, connected accounts, and quota. This unambiguously distinguishes it from the many data and mutation sibling tools, and 'Run this first' reinforces its preflight role.

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 gives explicit when-to-use guidance: 'Run this first before any other tool.' It does not name alternatives or state when not to use it, but the precedence instruction is clear and actionable.

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