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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds that results are paginated ('returns a page of leads') and maps to the Copper REST endpoint, which is useful context, but it does not say how to page through subsequent results or what the page envelope contains.

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?

Three short, front-loaded sentences, with the purpose first and the endpoint detail last. The REST endpoint line earns its place only for debugging/parity purposes; otherwise there is no waste.

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 12-parameter, zero-required search with no output schema, the description covers the essentials (search, optional filters, paged results) but omits page-traversal guidance and result-envelope shape. Adequate but with clear gaps.

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 100%, so every one of the 12 parameters carries its own description with filters, defaults, and bounds. The description only restates that filters are optional, adding nothing beyond the schema; baseline 3 applies.

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+resource ('Search/list leads') and clarifies that all filters are optional and a page of leads is returned. It is clearly distinguishable from the sibling search_* tools by resource, but it never explicitly names or contrasts them, so it stops short of the top band.

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?

'All filters optional' implies the tool can be called with no arguments, which is a genuine usage hint. However, there is no guidance on when to prefer this over copper_get_lead or the other search_* tools, and no exclusions or conditions.

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