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

With no annotations, the description carries the disclosure burden and does state 'Read-only', which is the key safety signal for this tool. It also discloses the returned fields. It stops short of mentioning ordering, completeness/limits, or auth requirements, which keeps it from a 5 for an unannotated tool.

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?

One compact sentence: the resource and scope come first, then the sibling comparison, then the intended consumers, then the safety note. Nothing is wasted and nothing important is buried.

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-only listing tool with no output schema, the description supplies everything needed to call it correctly: what it returns, why it exists versus its sibling, where to use the result, and that it is non-mutating.

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 the baseline is 4; there is no parameter meaning the description needs to add. The mention of returned fields is redundant with the eventual response but not harmful.

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 concrete resource (every pipeline of the workspace) and enumerates the returned fields (id, name, is_default), and explicitly positions it against the sibling crm_list_branches as the wider variant. An agent can distinguish it from crm_list_branches and crm_get_branch without opening any schema.

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?

It names the exact downstream tools that consume the result (crm_add_lead_to_branch / crm_move_lead_to_branch), so the selection condition is stated rather than inferred. It also explains why this variant is preferred over crm_list_branches, effectively covering the alternative.

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