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

Annotations already declare readOnlyHint, idempotentHint, non-destructiveHint and closed-world, so the safety profile is covered. The description adds that results are paginated, which is genuine extra context, but it says nothing about ordering, page-size limits, or what happens at the end of the result set.

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?

A single dense sentence front-loads the resource definition and tucks the box options and filtering into parenthetical clauses; nothing is wasted. It borders on crowded, which keeps it from a 5, but the structure is efficient.

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 5-parameter list tool with no output schema and low schema coverage, the description covers box selection, filtering and pagination, which is the core. It still omits the status enum values, paging defaults/limits, and result ordering, so an agent cannot fully predict the parameters or the return shape from the description alone.

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 20% (just the listing param), so the description does real work: it names the three box values, marks 'received' as the default, and describes status/listing filtering. But it never enumerates the status values (new/contacted/qualified/won/lost) or explains page/limit defaults, leaving the low-coverage schema only partially compensated.

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 (list) and resource (leads), then defines what a lead is ('inquiries received on their listings') and enumerates the three inboxes. This is far more than a restatement of the title. It doesn't explicitly contrast itself with the sibling get_lead (single lead) or set_lead_status, so it stops 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 gives useful context that 'received' is the default box and that results can be filtered by status or listing, which implies the normal usage pattern. However, it never says when to reach for this tool versus siblings like get_lead, search_listings, or list_my_tickets, and there are no exclusions.

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