list_groups

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description contributes only that IDs are stable across calls and that member route IDs are included, which is mildly useful; it says nothing about ordering, page size limits, or what an empty page means.

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?

It is a single short sentence with no filler or repetition. But it is a fragment that reads as an inventory of nouns rather than a front-loaded statement of what the tool does and when to use it.

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?

The presence of an output schema excuses it from describing return values, but with zero parameter documentation and a dense sibling catalog including create_group, add_track_to_group, and delete_group, the description does far too little to guide correct selection and invocation. Notable anomalies like a delete-confirmation flag on a read-only lister go unaddressed.

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 0%, and the single required `request` object hides six fields (limit, offset, dry_run, name_filter, confirm_delete, expected_revision) that are entirely undocumented anywhere. The description hints at pagination, which marginally maps to limit/offset, but it never explains name_filter, dry_run, or the surprising confirm_delete and expected_revision fields on a read-only list tool.

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?

"Paginate native route groups" names a verb and a resource, and adds that results carry stable IDs, properties, and member route IDs. However, it never explains what a "native route group" is or how it relates to the group tools among its siblings, so an agent reading only this would struggle to distinguish it from related listing tools.

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 when-to-use guidance at all: no indication of when to call list_groups versus inspecting tracks, plugins, sends, or the create/delete_group tools. The word "Paginate" implies iterative retrieval but gives no conditions, prerequisites, or exclusions.

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