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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds two useful facts: results are restricted to 'published' items and capped at '≤10 each'. It does not, however, explain pagination, what happens when no match is found, or the exact meaning of 'each'.

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?

A single terse sentence that leads with the search verb, which is good front-loading. However the '/compare marks' fragment and '≤10 each' are compressed to the point of ambiguity, trading clarity for brevity.

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, no-output-schema, read-only discovery tool the description covers scope, filterable fields, and a result cap, which is a reasonable minimum. It falls short on distinguishing this tool from the many sibling lookup tools and on clarifying the has filter's practical effect.

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 50% (query documented, has not). The description partially compensates by explaining that has= keeps items flagged positively in /compare, and by listing the queryable fields, but the seven enum values themselves are left to the schema and the has semantics remain vague.

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 clear verb (Search) over specific resources (published systems, tools, guides) and enumerates the match fields (name / vendor / category / kind word). It does not, however, clearly separate itself from siblings like renkeimap_system_facts or renkeimap_brief, leaving some ambiguity about when this discovery tool is preferred.

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?

The only usage signal is the cryptic phrase 'has= keeps those /compare marks positive', which implies filtering on comparison-positive items but never spells out when to use this tool versus renkeimap_compare or renkeimap_system_facts. No explicit when/when-not guidance or prerequisites are given.

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