tailscale_list_org_tailnets

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

Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond those: pagination behavior, a concrete default limit of 100, and the cursor-based termination condition. This gives the agent an accurate model of how the tool behaves at runtime.

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 three tight sentences that front-load the core purpose, then cover pagination and authentication with zero redundancy. Every sentence earns its place and no space is wasted.

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 listing tool with no output schema and fully documented optional parameters, the description is complete. It explains scope, pagination semantics, default behavior, termination condition, and authentication requirements, so an agent has everything needed to call it correctly.

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?

Schema description coverage is 100%, so the baseline is 3. The description goes slightly beyond the schema by explaining the pagination contract: pass the cursor back, and an empty cursor signals the last page. This adds useful semantic meaning to the 'cursor' parameter beyond its schema description.

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 ('List') and resource ('tailnets in your organization'), and adds the scope detail 'including API-only tailnets created via the API.' This clearly distinguishes it from related sibling tools like create_org_tailnet and delete_tailnet.

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 operational context: it explains pagination flow, the meaning of an empty cursor, and OAuth authentication requirements. It does not explicitly name alternatives or say when not to use this tool, but the listing semantics are unambiguous and the context provided is sufficient.

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