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 genuine context beyond annotations: the fact that all filters are optional and that it returns a page (pagination), plus the REST endpoint. It does not describe pagination limits or empty-result behavior, but is adequate given the low annotation bar.

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 zero filler; the tool's purpose leads. The endpoint line is marginally useful but earns its place as an implementation hint.

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 10 optional params, a read-only annotation and no output schema, the description covers the essentials but is thin. It could say what fields are returned or how paging behaves, though the schema already covers filters and pagination params.

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 the schema fully documents all 10 parameters (city, name, tags, sort_by, page_size, etc.). The description only adds the meta-statement that all filters are optional, which is baseline-consistent with 0 required params. No syntax or semantic detail 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') and resource ('companies'), and the description is clearly distinguishable from the sibling search_people/search_leads/search_opportunities tools because the resource differs. It does not explicitly name alternatives, but the resource is unambiguous.

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?

'Search/list companies. All filters optional' implies the tool is used for broad retrieval with optional narrowing, but there is no explicit statement of when to use this versus copper_get_company (single lookup) or the create_* siblings. Usage is inferred rather than stated.

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