everything_recent

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose the meaningful trait that results are sorted newest first, but says nothing about result limits, pagination, or scope/permission requirements for reading files across shares.

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 purpose leads, followed by three tight parameter lines with no filler. Every clause carries information the schema does not already contain, notably the enum-like values for 'within' and the delimiter for 'extensions'.

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 simple filtered-list tool with no output schema and no annotations, the description covers the discovery-critical semantics: what is returned, its order, and how to filter by path, type, and time. The remaining gap is the undocumented 'limit' parameter and default of 50, which an agent may need to reason about.

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 0%, so the description must compensate, and it documents three of four parameters well: path_filter's scope ('a folder or share'), extensions' delimiter and example ('xlsx;csv'), and the accepted 'within' values including a concrete month format. Only 'limit' is left entirely undefined in both schema and description.

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?

States a specific verb and resource ('Most recently modified files') plus the sort order ('newest first'), which is enough to distinguish it from siblings like everything_largest or everything_count. It never names those siblings explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied by the name and the sort-order statement, but there is no explicit 'use this when...' guidance and no mention of when to prefer everything_search or everything_semantic_search instead. The only routing-adjacent content is parameter-value guidance for 'within', which is not the same as usage guidance.

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