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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds that results are paged with skip/take and that clients are contacts, but it does not provide additional behavioral context such as return shape, default ordering, or pagination 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?

A single front-loaded sentence with no wasted text. The scope clarification and paging behavior are packed efficiently without burying the main action.

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 read-only list tool with 9 optional parameters and no output schema, the description covers the core purpose and common filters but omits guidance on advanced filter objects and sorting. It is minimally adequate but not complete enough to fully guide complex usage.

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 56%, so the description must compensate and it partially does by naming name, email, type, and update-date filtering plus paging. It leaves advanced 'filters', sort_by, and sort_order unexplained, so parameter meaning is only partially enriched.

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 contacts') and clarifies scope by including people, companies, and clients. It does not explicitly distinguish itself from siblings like lawcus_search or lawcus_list_leads, 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?

Gives implied usage through filterable fields and paging, which helps an agent know how to narrow results. However, it does not say when to use this tool instead of lawcus_search, lawcus_get_contact, or lawcus_list_leads, so there is no explicit alternative routing.

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