arcana_grep

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

With no annotations, the description carries full burden. It reveals the search engine behavior (FTS5 vs Python re) but omits side effects, performance implications, or whether it is read-only. Adequate but incomplete for a search tool.

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?

Description is concise with a header and Args list. Front-loaded with the core purpose. All listed parameters are covered, though some could benefit from more detail. Good efficiency.

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?

Output schema exists, covering return values. The tool has 3 optional params, but description omits behavior with empty pattern or default uri scope. Adequate but missing contextual details.

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 0%, so description must compensate. It explains 'pattern' can be keyword or regex and 'case_insensitive' is boolean, but no examples syntax or details on 'uri' semantics beyond default. Insufficiently detailed for full understanding.

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 clearly states the tool performs keyword/regex search, specifying FTS5 for simple terms and Python re fallback. This distinguishes it from sibling tools like arcana_search or arcana_find by giving engine details.

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 explicit guidance on when to use this tool versus alternatives. The description implies keyword/regex use but does not mention when not to use it or cite alternative tools like arcana_search or arcana_find for different search needs.

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