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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description's only added behavioral fact is that this is an alias, i.e. its behavior mirrors parse_search, with no detail on results, limits, or side effects.

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 short sentences, zero filler, with the alias identity front-loaded before the usage condition. Nothing to trim.

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 two-parameter, read-only alias with no output schema this covers the routing question adequately, and the rich annotations handle safety. It is still silent on what a search returns, how the limit behaves, and whether parity with parse_search is exact in every respect.

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 50% — 'query' is documented in the schema but 'limit' is bare — and the description adds nothing about either parameter. It does not explain what a query can be, nor the 1-10 limit bound or its default, so it fails to compensate for the coverage gap.

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?

The description states a specific relationship ('Compatibility alias for parse_search') and the resource it fronts ('generic search tool'), so an agent can identify it as the alias twin of a named sibling. It does not say what is actually searched, but the alias framing plus the named target tool make the purpose identifiable.

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?

It gives an explicit selection rule: 'Use for clients that expect a generic search tool.' That is a genuine when-to-use condition and it implicitly routes the agent to parse_search as the canonical equivalent. It omits any when-not guidance or query-shape advice, so it is clear but not complete.

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