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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the read-only nature is established by structured data. The description adds only the organizational scope ('available in an organization'), which is mildly useful but does not disclose pagination, filtering, or what 'available' 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?

The description is a single front-loaded sentence with no filler, and every word carries purpose. It is concise, though the 'tags' versus 'labels' wording creates minor ambiguity and the terseness contributes to incomplete guidance elsewhere.

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 four parameters, no output schema, and no parameter descriptions, this minimal description is not complete. It fails to clarify the search and pagination parameters, what 'available' means, or how this tool relates to similarly named sibling tools, leaving an agent to guess.

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%, so the description must compensate for the four parameters, but it only hints at orgId via 'in an organization.' It provides no meaning for limit, offset, or search, leaving the agent without guidance on how pagination and filtering work.

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 ('List'), resource ('process tags'), and scope ('in an organization'), making the basic purpose clear. However, it uses 'tags' instead of 'labels' and does nothing to distinguish this tool from the near-identical sibling listAvailableClarityProcessLabels, so it misses the top score.

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?

The phrase 'available in an organization' implies this is the tool to use when retrieving org-scoped process labels, so there is some implicit usage guidance. But there are no explicit when-to-use conditions, no exclusions, and no mention of alternatives such as listClarityProcessAssignedLabels or listAvailableClarityProcessLabels.

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