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

With no annotations, the description carries the full burden and does well: it declares the tool read-only and enumerates the exact return fields (id, name, is_default, member_user_ids), including the "General" default marker. It omits any note on auth/permissions or whether an empty list is possible.

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?

Three dense sentences ordered definition → return shape → usage, each earning its place. The parenthetical "(teams / directions / clients)" is slightly cryptic but acts as a quick synonym gloss.

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-param list tool with no annotations and no output schema, the description supplies the missing return-value information and the downstream call pattern. Only the differentiation from crm_list_all_branches is left uncovered.

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 schema baseline is 4. The only parameter-like guidance (passing branch=<id> or "general" downstream) is useful context for the follow-up calls rather than this one.

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 defines the resource precisely ("isolated pipelines inside one workspace") and lists the fields it returns, which makes the operation unmistakable. It does not explicitly distinguish itself from the close sibling crm_list_all_branches, so an agent must infer that one is workspace-scoped and the other cross-workspace.

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?

"Call before crm_stats / crm_list_leads when the user has more than one branch, then pass branch=<id>" gives explicit ordering, a precondition, and the follow-up action. No exclusion is stated against crm_list_all_branches or crm_get_branch, so the sibling routing is incomplete.

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