Check the Depot token and its visible scope

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

The description goes beyond the readOnly/idempotent annotations by disclosing that it reports visible organizations/projects, always indicates no mutating capabilities, and never returns the token itself. This gives the agent important security and expectation-setting context not present in annotations.

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 front-loaded with the core purpose and then adds usage guidance and security notes. It is slightly longer than strictly necessary, but each paragraph covers a distinct and valuable aspect, so the verbosity is justified.

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 zero-parameter diagnostic tool with an output schema and strong annotations, the description is complete. It covers when to call it, what it reports, a common failure scenario, and the crucial guarantee that it never exposes the token. Nothing essential is missing.

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 input schema has zero parameters, so the baseline is 4 and parameter documentation is unnecessary. The description appropriately focuses on what the tool returns rather than inputs, which is all that is needed here.

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 states a specific verb and resource: 'Verify the configured Depot token and report which organizations and projects it can actually see.' This clearly distinguishes it from the list/get/diagnose sibling tools and makes its diagnostic role 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?

It explicitly instructs the agent to call this tool first 'whenever another Depot tool returns an empty list or a permission error,' and explains the underlying failure mode. This is concrete, actionable guidance that an agent can apply without inference.

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