search_recent

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

No annotations are provided, so the description must disclose behavioral traits itself. It mentions performance but does not state that this is a read-only operation, what output format is returned, or any limitations like symlink handling. The non-destructive nature is implied but not explicit.

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 concise sentences that front-load the purpose and add a performance note. Every word earns its place with no filler.

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 tool is simple with inputs fully documented, but there is no output schema, and the description does not mention what the results look like (e.g., file paths). This leaves some ambiguity about the return value, but the core behavior is understandable.

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 covers all 4 parameters with descriptions at 100% coverage, so the schema does the heavy lifting. The description adds nothing beyond the 'N hours' concept, staying at the baseline 3 for full schema coverage.

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+resource+qualifier: 'Find files modified within the last N hours.' This clearly distinguishes it from sibling tools that search by content or path. The focus on recency is 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?

States this is the fastest way to find recently changed files and directly compares to 'find -mtime' as a slower alternative, providing clear context for when to use it. However, it does not explicitly mention when to use sibling search tools or provide exclusionary guidance.

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