registry_search

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

No annotations exist, and the description does not disclose behavioral traits such as read-only nature, performance impact, or permission requirements. The word 'search' implies a read operation, but this is not explicitly stated, leaving ambiguity.

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?

While very concise (one sentence), the description is under-specified. It does not earn its place because it fails to convey necessary details about the tool's behavior or parameters, making it more of a title than a useful description.

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 tool has 5 parameters, no output schema, and no annotations, the description is severely incomplete. It omits crucial information such as the meaning of parameters, return format, and any side effects, leaving the agent with insufficient context to use the tool correctly.

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%, and the description adds no meaning beyond the parameter names and types. For example, 'pattern' is never explained (e.g., regex format or wildcard support), and 'search_names' and 'search_data' are not described. The tool's core logic is unclear.

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 'Search registry values by pattern.' clearly states the action (search), the resource (registry values), and the method (by pattern). It distinguishes itself from sibling registry tools like registry_get_key (which retrieves a specific key) by focusing on pattern-based search across values.

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?

No guidance is provided on when to use this tool versus alternatives. The description lacks any context about prerequisites, preferred scenarios, or exclusions (e.g., 'Use registry_get_key for exact key lookups').

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