list_groups

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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds the genuinely useful disclosure that the result set may be silently capped and how to detect it via `truncated` — behavior an agent could not infer from the annotations or schema.

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: the first enumerates content, the second front-loads the truncation caveat. No filler, nothing repeated from structured fields beyond a brief field list.

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 single-optional-parameter read tool with full annotation coverage and an output schema, this is enough: the only non-obvious risk (incomplete results) is explicitly called out, and return-value details are delegated to the output schema.

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 coverage is 100% and `limit` is already documented there as 'Maximum items to return (server default if omitted).' The description reinforces the capping semantics but adds no syntax or default details beyond the schema, so the documented-schema 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?

Opens with a specific verb+resource ('List Twingate groups') and names the fields returned (id, name, type, active, member count), which immediately separates it from the sibling list_users / list_resources / list_connectors tools. An agent can select it without opening the schema.

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 gives clear operational guidance: results are capped by `limit`, and if `truncated` is true the caller must not treat the list as complete. It stops short of naming alternatives or stating exclusions (e.g. when to use list_users instead), so it's clear context without explicit routing.

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