List Groups Labels

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get All' hints at a read operation but discloses nothing about pagination behavior despite page/perPage/paginationSeed parameters, filtering semantics, authentication needs, or response characteristics beyond what the output schema provides.

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?

At two words, this is under-specification rather than conciseness. There is nothing verbose or misplaced, but the description carries almost no information and does not earn its place as a meaningful tool definition.

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 tool with 9 parameters, no annotations, 0% schema coverage, and a large sibling family, 'Get All' is wholly inadequate. The output schema may cover the return shape, but all selection context, parameter semantics, and behavioral expectations are missing.

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 description adds zero meaning for any of the 9 parameters. Opaque parameters like queryFilter, paginationSeed, and orderByNullPosition are entirely undocumented in both schema and description, and 'Get All' does nothing to compensate for this gap.

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 'Get All' conveys a retrieve-all operation but never names the resource (labels) or scope (groups), leaving the title and tool name to carry all the meaning. It essentially restates the 'List' prefix of the name without distinguishing this tool from sibling read tools like list_organizers_tags or get_groups_labels_by_item. This borders on tautology.

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 guidance whatsoever on when to use this tool. With a large sibling family that includes list_organizers_tags, list_organizers_categories, list_organizers_tools, and get_groups_labels_by_item, an agent has no basis to choose between this and the alternatives. No exclusions or alternative tool references are provided.

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