groups_multi_purpose_labels_get_all

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

No annotations are provided, so the description carries the full behavioral burden. It only implies a safe read via 'read-only' in the keyword list; it does not disclose pagination behavior, authentication requirements, scope of the label list, or any operational constraints despite having eight parameters.

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 core statement 'Get All — Groups: Multi Purpose Labels. List labels.' is short and front-loaded, but the large keyword block is repetitive and adds little semantic value. The overall text is bloated rather than efficiently structured.

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 an eight-parameter list endpoint with no output schema, no annotations, and 0% schema description coverage, the description is far too thin. It omits pagination, filtering, sorting, authentication, and return behavior, leaving an agent without the context needed to invoke the tool 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 0%, and the description adds no meaning for parameters such as page, search, orderBy, perPage, queryFilter, orderDirection, paginationSeed, or orderByNullPosition. With eight undocumented parameters, the description does not compensate for the schema's lack of 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 states a specific verb and resource: 'Get All — Groups: Multi Purpose Labels. List labels.' The 'Get All' wording distinguishes it from the sibling get_one operation. However, it does not explicitly contrast itself with other label-related siblings such as create_one, update_one, or delete_one.

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, no prerequisites, and no mention of alternatives. The keyword list includes search, find, browse, fetch, and read, but these do not explain when an agent should choose this tool over siblings like groups_multi_purpose_labels_get_one.

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