check_drive_connection

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

With readOnlyHint and openWorldHint already declared, the description goes well beyond annotations: it explains the JWT signing mechanism, that it probes a nonexistent delivery, and decodes the outcome (404 = authenticated, 401 = wrong key). It also discloses that it reports the routed environment (sandbox/production), giving the agent real behavioral context a mere read-only hint cannot.

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 tight sentences, front-loaded with the main purpose (verify the key) before the mechanics and the secondary environment report. Every clause carries information; nothing is redundant padding.

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?

Despite having no output schema, the description explains what the return signals mean (404 vs 401) and what extra data comes back (environment). For a zero-parameter diagnostic tool, an agent has everything needed to call and interpret it.

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?

This tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline for parameterless tools is 4. No parameter-related gap exists to compensate for.

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?

States a specific verb+resource (verify your Drive access key) and immediately distinguishes itself from the dispatch-heavy siblings by clarifying it dispatches nothing. An agent can tell this is a credential/connectivity check rather than a delivery action without inspecting anything else.

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?

Gives clear context for when to use it (to validate a locally-held key) and explicitly notes it does not dispatch, which separates it from dispatch_delivery and friends. It stops short of naming an alternative tool or stating exclusions such as 'do not use this to check account state — use get_account', so it is clear but not fully routing.

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