list_open_documents

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

No annotations are provided, so the description carries the behavioral burden. It does disclose the return type (a list of open document summaries), which is useful. However, it says nothing about side effects, read-only guarantees, behavior when no documents are open, or error conditions; for a simple 'list' operation, the omission is moderate rather than severe.

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 and front-loaded: the main action is stated in the first sentence, and the Returns line adds necessary information without any filler. Every sentence earns its place.

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 zero-parameter list operation with an output schema present, the description is largely sufficient. It states the resource and the shape of the return value. It could be more complete by explicitly clarifying that it only reflects documents open in the current session, but that is strongly implied by the name and description.

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 zero parameters, so there is nothing for the description to elaborate on. The input schema already fully covers the parameter surface, and the baseline for zero-parameter tools is 4.

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 a specific verb ('List') and resource ('all currently open documents'), making the tool's purpose immediately understandable. It does not explicitly differentiate itself from siblings like get_document_info or get_document_summary, but the phrase 'currently open documents' is distinct enough for most cases.

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 implies that this tool should be used to retrieve currently open documents, but it gives no explicit when-to-use/when-not-to-use guidance and does not name alternatives. With a large sibling list that includes open_document and close_document, some explicit context would help, but the intent is still inferable.

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