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

No annotations are provided, so the description carries the full burden; it does at least self-declare 'Read-only', which is the most important safety signal. It says nothing about behavior for a lead with no pipelines, whether archived/closed pipelines are included, or what happens if the id is invalid.

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 compact sentences, zero filler, with the return content front-loaded and the read-only note trailing. Nothing is redundant with the title or schema.

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 single-parameter read tool with no output schema, describing the returned fields (stage, owner per pipeline) is close to sufficient. Minor gaps remain around empty results and pipeline scope, but nothing an agent would likely get wrong when calling 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?

There is a single required parameter and schema description coverage is 100% ('Lead id (UUID)'), so the schema fully documents it. The description adds no extra semantics about the id beyond what the schema states, so the baseline 3 applies.

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?

States a specific verb-resource pair: returns every pipeline (branch) a lead sits in, plus stage and owner per pipeline, which also disambiguates the 'branches' naming in the tool name. It does not name sibling alternatives such as crm_get_lead or crm_list_branches, so an agent still has to infer the boundary.

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 explicit when-to-use framing, no exclusion (e.g., use crm_get_lead for lead fields, crm_list_branches for all pipelines in the workspace), and no prerequisites. The usage is only implied by the phrase 'a lead currently sits in'.

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