Claude Code: Full-Text Search

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive. The description adds 'Default 6h', which implies a default time window for the 'since' parameter, but does not disclose other behaviors like result ordering, limits, or pagination. Value-add is moderate.

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?

Two sentences with no extraneous information. Everything is front-loaded: purpose and a key behavioral default. Highly efficient.

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 search tool with many siblings and no output schema, the description is adequate but minimal. It covers purpose and a default but omits return format, pagination, result count, or error scenarios. Annotations fill some gaps but not fully.

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 100% with descriptions for both 'term' and 'since' parameters. The description adds implicit default for 'since' (6h), which is not in the schema. This provides additional practical guidance beyond the schema.

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 it performs full-text search across 'Claude Code message and tool bodies for a substring', which is specific and distinct from sibling tools like 'search' or 'claude_errors'. The verb 'search' and resource are explicit.

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 on when to use this tool vs alternatives (e.g., 'search', 'claude_errors'). The description mentions 'Default 6h' but does not explain optimal contexts or exclusions. Lacks explicit when-to-use or when-not-to-use advice.

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