List lead reports

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

Annotations (readOnlyHint=true, idempotentHint=true, destructiveHint=false) already indicate safety and idempotency. Description adds only the word 'Report', offering no additional behavioral context (e.g., pagination, default limit, sorting, or if the response includes summaries).

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?

Single sentence, no redundancy. However, it sacrifices necessary detail for brevity, which harms overall usefulness.

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?

With 15 parameters, zero schema descriptions, no output schema, and a bare-bones description, the tool is severely underdocumented. Agent cannot infer return format, pagination behavior, or valid parameter combinations.

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% — no parameter descriptions. Description mentions 'status, permission, district, owner, and volume summaries', which maps to some params (status, permissionStatus, district, ownerId, includeSummary), but critical params like limit, offset, search, groupBy, leadId, etc. are unexplained. Agent would lack understanding of filtering and pagination.

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?

Description says 'Report on client leads' which is ambiguous — it could imply generating a report rather than listing. Title clarifies 'List', but within description, the purpose is somewhat vague. Does not differentiate from sibling list tools like limu_list_client_profile_reports.

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?

No guidance on when to use this tool versus alternatives like limu_get_lead_report (which seems to fetch a single report). No mentions of use cases, prerequisites, or exclusions.

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