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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety traits. The description adds 'paginated,' which confirms pagination behavior, but this is also evident from the page/limit parameters. It does not disclose additional behavioral details such as pattern syntax or result ordering.

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?

The description is a single, front-loaded sentence: 'Search CPEs by pattern (paginated).' It is concise, with no redundant words, and directly states the tool's purpose.

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?

Given the simple read-only, paginated search tool with an output schema, the description is minimally adequate. However, it lacks pattern syntax details and usage differentiation from sibling search tools, leaving room for confusion. The output schema likely covers return values, reducing the burden.

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 0%, so the description must compensate. It only clarifies that cpe_pattern is a 'pattern,' but does not explain the pattern syntax (e.g., regex, wildcard, substring). Page and limit are implied by 'paginated' but not defined. This is minimal compensation for the lack of schema descriptions.

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 uses a specific verb ('Search') and resource ('CPEs') with a clear modifier ('by pattern'), making the tool's function immediately clear. It distinguishes from sibling tools like get_cpe_by_scan, which fetches CPEs for a specific scan.

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 phrase 'by pattern' implies the tool is used when searching CPEs via a pattern, but it does not explicitly state when to use this versus alternatives. No mention is made of other search tools or exclusions, so only implied usage guidance is present.

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