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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds the underlying REST call (GET /tailnet/{tailnet}/keys), which is useful provenance, but says nothing about ordering, pagination, or the scope requirement needed to see other users' keys beyond what the schema already notes.

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 short sentences with no filler; the core capability is stated first and the REST reference trails as supporting detail. Nothing could be removed without losing 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?

For a read-only list tool with a single optional boolean, no output schema, and annotations covering safety, the description plus schema is nearly sufficient. Only the relationship to the sibling get/create/delete key tools is missing, which is a minor gap.

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?

With 1 optional parameter at 100% schema description coverage, the schema fully documents the 'all' flag including its scope caveat and default. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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?

A specific verb (List) plus a well-defined resource (auth keys and API access tokens for the tailnet), and the REST endpoint mapping pins the exact operation. It is distinguishable from siblings like tailscale_get_key (singular fetch) and tailscale_create_auth_key (mutation), though it never names them explicitly.

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?

There is no statement of when to choose this tool over tailscale_get_key or how it relates to tailscale_create_auth_key/tailscale_delete_key. The only hint of usage is the scoping concept embodied in the 'all' parameter, and that lives in the schema rather than the description. Implied usage at best.

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