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

Annotations only declare readOnlyHint=true, so the description must carry return-shape disclosure — and it does, listing client, year, summary, results, outlets and a link, plus the empty-query default behavior. With no output schema, this is valuable context; rate limits, pagination beyond the limit param, and result ordering beyond 'most recent' are not covered.

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 tightly written sentences with no filler: the first establishes what is searchable and over which dimensions, the second discloses the result shape and the empty-query default. The core capability statement is front-loaded.

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 three-parameter, zero-required, read-only search tool with no output schema, the description supplies the two things an agent most needs: what fields results contain and what happens with an empty query. Only minor gaps remain, such as result ordering when a query is supplied.

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 parameters — including the enum values for business and the limit bounds — are fully documented in the schema. The description echoes the query semantics ('by client, industry, market or keyword') and the empty-query case but adds no syntax or format detail beyond the schema, so the 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 (search) and resource (iMpact's client case studies), then enumerates the topical domains covered (PR launches, media coverage, crisis, GEO, corporate training). This is easily distinguishable from the sibling tools get_company and send_inquiry, which are an entity lookup and a write action respectively.

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?

Names the searchable dimensions (client, industry, market, keyword) and explains the fallback behavior for an empty query (returns most recent), which tells the agent how to invoke it with no criteria. It does not name alternatives or exclusions, but the sibling tools are functionally unrelated, so there is little to distinguish against.

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