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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the cost is free, the payload shape is enumerated, and list_id alters scope rather than adding a filter dimension. It does not address auth, though the schema does.

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 core payload contents are front-loaded in the opening clause, with the list_id scoping and cost note trailing. The enumerated metric list is dense but every item is a real return field; the one-word 'Free.' sentence is terse and useful rather than filler.

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 read-only, zero-required-parameter summary tool with no output schema, the description effectively doubles as the return-contract by listing every reported aggregate. The only missing piece is a hint that this is the natural entry point before drilling into individual leads or lists.

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 100%, so uid, list_id and bearer_token are all documented and the baseline of 3 applies. The description restates the list_id scoping behavior already in the schema and says nothing about uid or bearer_token, so it adds no meaning beyond the structured fields.

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 resource and deliverable: a CRM pipeline summary plus the user's custom lists, enumerating exactly what aggregates come back (creators per stage, in-conversation counts, committed deal value, tasks due, list id/name/size). The aggregate-count framing makes it obviously distinct from list_crm_leads and manage_crm_list without having to name them.

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?

Only guidance offered is the conditional 'Pass list_id to scope the pipeline to one list' and the note that it is free. There is no explicit statement of when to reach for this overview versus list_crm_leads or manage_crm_list, so the when-to-use is implied rather than stated.

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