find_recent

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

With no annotations provided, the description should disclose behavioral traits beyond the basic purpose. It only mentions sorting by date but does not reveal that it recursively traverses directories, respects include/exclude patterns, or that it is a read-only operation. Important details like depth limits and result caps are left to the schema, which the agent may not infer.

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 a single sentence of 10 words that immediately conveys the core action and ordering. Every word adds value, and no extraneous information is present. It is appropriately sized and front-loaded for an AI agent to quickly understand the tool's main function.

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 and no output schema, the description is too minimal to provide a complete understanding. It does not explain the behavior of the depth traversal, filtering via include/exclude, or the format of the returned results. The agent would need to rely entirely on the schema for details, which may not be sufficient for effective usage.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for each parameter. It does not elaborate on how to use the parameters together or what the output includes, but the schema descriptions are adequate.

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 verb 'Find', the resource 'most recently modified files under a directory', and the sorting behavior 'sorted by date descending'. This is specific and distinguishes it from siblings like 'list_directory' (lists all files) or 'search_by_date' (likely searches by date range).

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 does not provide any guidance on when to use this tool versus its siblings. It lacks explicit context such as 'Use this to find recently modified files; for other search criteria, use find_largest or search_by_date instead.' The usage context is only implied by the tool's name.

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