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

readOnlyHint=true already establishes the safe-read profile. The description adds that results come back as a page and cites the underlying REST endpoint (POST /opportunities/search), which is real extra context, but says nothing about auth requirements, rate limits, or the shape of returned records.

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 compact clauses with the core purpose front-loaded, then the filter/pagination behavior, then the implementation note. No filler, nothing redundant.

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 paginated search with full schema documentation, the description covers purpose and paging, but with no output schema it could say more about what a returned opportunity contains or how paging metadata is exposed.

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 100% and each of the 11 filters is documented in-schema, so the baseline of 3 applies. The description only restates that filters are optional and adds no format or cross-parameter semantics beyond the schema.

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 (search/list), resource (opportunities/deals), and adds the helpful synonym 'deals'. It is distinguishable from copper_get_opportunity (single fetch) and copper_create_opportunity, though it never names those siblings explicitly.

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' usefully signals the tool can be called with no arguments to page through everything, but there is no explicit when-to-use guidance versus copper_get_opportunity or the other copper_search_* tools, and no exclusions.

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