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

The readOnlyHint=true annotation already establishes this is a safe read; the description adds no behavioral context beyond that — no scope, no pagination, no ordering, no note on whether labels are global or per-project. It does not contradict the annotations, but it contributes nothing they don't already say.

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?

Two words with zero waste, but this is under-specification rather than disciplined concision — the sentence is too short to convey the scope an agent needs. It is at least front-loaded with the verb.

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 zero-parameter read tool with an explicit readOnlyHint, the description is minimally sufficient to attempt a call. However, with no output schema and no statement of what set of labels is returned, the agent cannot predict the result before invoking it.

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?

The tool takes zero parameters, so there is nothing to document and the baseline of 4 applies. The empty schema is self-explanatory and needs no elaboration from the description.

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?

"List labels." states a verb and a resource, so the basic intent is legible, but it never says whose labels (task, project, workspace) or what the result covers. It is also not distinguished from siblings such as taskhold_list and taskhold_list_projects, which an agent could easily confuse with it.

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 on when to call this instead of taskhold_list, taskhold_list_projects, or taskhold_search. The agent must infer the use case entirely from the tool name.

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