list_leads

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the real dependency on list_views, which is useful, and 'List' implies a read-only operation, but it says nothing about pagination behavior despite page/per_page existing, nor about result ordering or limits.

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 short sentences, zero filler, with the operation stated first and the prerequisite immediately after. Nothing in it is redundant with the name or title.

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?

The essential prerequisite is covered, which is the most important thing an agent needs. But with no annotations, no output schema, and three undocumented parameters, the description leaves pagination and return-shape behavior entirely unaddressed for a list tool that plainly supports paging.

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 only 40%: sort and view_id are documented in-schema, while page, per_page, and sort_type have no descriptions. The description only alludes to view_id indirectly via the list_views instruction and adds nothing about pagination or sorting semantics, so it fails to compensate for the coverage gap.

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 leads') and scopes it ('from a saved view'), which separates it from the sibling search_leads by implying view-driven rather than query-driven retrieval. It stops short of naming search_leads explicitly, so differentiation is inferable rather than stated.

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?

Gives a concrete prerequisite and call order: 'Call list_views(module="leads") first to get a view_id.' That is actionable guidance an agent can follow without guessing. It does not, however, state when to prefer this over search_leads or what to do if the view returns nothing.

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