list_documents

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

No annotations are provided, so the description must convey behavioral traits. It indicates the tool lists 'currently open' documents, implying a read-only operation with no destructive side effects. However, it does not explicitly state that it is non-modifying, but the verb 'list' and the context of OmniPlan suggest safety.

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 extremely concise: two sentences with no wasted words. The core purpose is front-loaded, and the note provides additional context without 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?

For a simple no-parameter list tool, the description covers the essential behavior (listing open documents) and the note about task tools adds valuable context. The existence of an output schema handles return values, so no further details are needed.

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?

The tool has no parameters, so the input schema fully covers them. The description adds no parameter information because none is needed, meeting the baseline for zero 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 'List all currently open OmniPlan documents,' which is a specific verb ('list') and resource ('documents'), and distinguishes this tool from sibling tools like list_assignments or list_resources by focusing on documents.

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 provides context that listing documents is about open documents, and the note about task tools operating on the current front document hints at when this tool might be used (e.g., to check which document is active), but it does not explicitly state when to use this versus other list tools.

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