list_leads

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

With no annotations, the description carries the full burden. It usefully discloses that results are scoped to the 'active mesh' (implying a dependency on set_active_mesh), but says nothing about pagination, result limits, permissions, or read-only safety. Some genuine context, but far from complete.

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 tight sentences, purpose first, filter semantics second. No filler and nothing redundant with the 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?

An output schema exists, so return values need not be explained, and the one parameter is covered. However, with no annotations and no mention of pagination or volume expectations for a list operation, an agent lacks confidence about result set size and iteration.

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 coverage is 0% and the single `stage` parameter is undocumented in the schema, so the description's note that it accepts a stage name or UUID provides real added meaning. It stops short of describing default/null behavior or valid stage values.

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 ('List CRM leads') and a scoping constraint ('in the active mesh'), which separates it from create_lead and move_lead_stage siblings. It does not explicitly differentiate itself from the other list_* siblings, so it falls just short of a 5.

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?

The description says what the tool returns but never when to reach for it versus alternatives like list_contacts or search_chat, and offers no prerequisites or exclusions. Usage is only implied by the verb 'List'.

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