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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: the ordering of results mirrors the user's account setup, names/IDs are account-specific rather than defaults, and it names the auth requirement (Cotlet API key with access to the app).

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?

Front-loaded with what is returned, then the actionable note about IDs, then the auth requirement. Slightly repetitive in restating the account-ordering idea twice ('as set up in your account' / 'in the order set in your account'), which costs it the top mark.

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?

No output schema and no parameters, so the description must carry the return-shape burden, which it does: pipelines, their statuses, ordering, and ID semantics. Safety is already covered by annotations. It is close to complete for a simple read-only lookup; only the concrete response field names are unspecified.

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 are zero parameters, so per the rubric the baseline is 4. The description correctly signals a no-input listing call, with no misleading parameter references.

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 and resource ('list pipelines'), and further specifies the payload: pipelines plus the statuses in each, with IDs. An agent immediately knows this retrieves account-configured pipeline/status taxonomy rather than leads or tasks.

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 does not frame when to call this versus alternatives, but it does give the downstream usage context: use the returned IDs in list_leads and update_lead_status. That is implied usage rather than explicit selection guidance, so it lands at the minimum-viable tier.

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