Search Rules and Skills

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

Annotations declare the tool as read-only, non-destructive, and idempotent. The description adds context about the return format (matching names, descriptions, rule excerpts with line numbers), enhancing transparency beyond the annotations.

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 concise with a clear purpose statement followed by an args section. No extraneous words, well-structured, and front-loaded with key information.

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?

The description covers the search target, parameters, and return format. With annotations providing safety traits and no output schema needed, the description is complete for the tool's complexity. The sibling tools context confirms this search tool is distinct.

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 schema already fully documents both parameters. The description adds return info but does not provide additional semantics for the parameters beyond what the schema offers, meeting the baseline of 3.

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 name and title clearly state the tool's purpose. The description provides a specific verb ('Keyword search') and resource ('skill descriptions and global rule file contents'), distinguishing it from sibling tools like rules_get_skill and rules_get_global that retrieve specific items.

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 description implies usage when searching across skills and rules, but does not explicitly state when to use this tool over alternatives. However, given the sibling tools are all retrieval/get operations, the search purpose is distinct and clear enough.

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