list_recently_opened_documents

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action without details on read-only nature, sorting, limits, or any side effects. The agent cannot infer important characteristics like whether this is a safe read operation or if it requires specific permissions.

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 that conveys the essential information efficiently. It could be slightly more descriptive (e.g., mentioning the output format), but it is not verbose and avoids redundancy.

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?

With no parameters and an output schema, the description is minimally sufficient. However, it lacks context about the read-only nature, the meaning of 'recently opened', or any ordering. Given the simplicity, a score of 3 is appropriate as there is room for improvement without being inadequate.

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?

There are zero parameters, so the input schema provides full coverage. The description adds no parameter-specific info but is consistent. For zero-parameter tools, the baseline is 4, and the description adequately explains the purpose without needing to elaborate on parameters.

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 lists recently opened documents for the current user. The verb 'list' and resource 'recently opened documents' are specific. However, it does not explicitly differentiate from siblings like list_documents or search_documents, though the qualifier 'recently opened' provides implicit distinction.

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 versus alternatives. The description only states the action and scope, but lacks context such as 'Use when you need to see the user's recent documents, as opposed to all documents (list_documents) or searching (search_documents).'

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