listTagGroups

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description adds significant behavioral context: cursor-based pagination details (limit, page), filter/sort capabilities with references to rules, and the exact return structure. No contradictions.

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 well-structured with clear sections: title, use when, pagination, filter/sort, see also, returns. Every sentence adds necessary information without redundancy. It is concise but comprehensive.

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?

Given 7 parameters, no output schema, but rich annotations, the description covers all essential aspects: what it returns (status, pagination info, records), how pagination works, filtering/sorting options, and when to use. It is complete for an enumeration tool.

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%, so the description's job is lighter. However, it adds value by grouping parameters into pagination and filter/sort sections, summarizing operator types, and referencing external rules for full details. This goes beyond the schema's individual descriptions.

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 clearly states 'List tag groups - Paginated enumeration of taggroup records. Read-only.' It specifies the verb (list), resource (tag groups), and key trait (paginated, read-only). It distinguishes itself from the sibling tool getTagGroup (single record by ID).

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?

Explicitly states 'Use when: discovering the tag groupings before creating tags - each tag belongs to a group.' Provides a clear context for when to use this tool. Also references getTagGroup as an alternative for single record retrieval.

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