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

readOnlyHint=true already declares the safe-read profile, and openWorldHint=true signals firm-scoped data. The description adds that results carry contact details and pipeline stage, and that responses are paged, but says nothing about page-size limits, ordering defaults, or total-count behavior beyond the schema.

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, front-loaded with what the tool returns, no filler. The 'Paged with skip/take' clause is mildly redundant with the schema but earns its place as a pagination cue.

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 9-parameter listing tool with no output schema, the description omits any mention of the filtering, sorting, and stage/source-id narrowing capabilities, which are the main decision points for an agent. Adequate for a basic list call, incomplete for the surface the schema exposes.

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 67%, so the schema documents most params (skip/take/filters/stage_id/lead_source_id). The description only echoes pagination via skip/take and adds no meaning for the filter array, sort_by/sort_order, or name_contains; baseline 3 is appropriate given coverage but no extra value.

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 clarifies the domain term with '(prospective matters)', plus what comes back ('client contact details and pipeline stage'). It does not contrast with the closest sibling lawcus_get_lead or lawcus_search, so it falls 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?

No statement of when to call this vs lawcus_get_lead (single lead), lawcus_search (query across entities), or how filtering should be routed between named params and the 'filters' array. Only an implied read-all-listing usage is conveyed.

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