List Documents

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

Discloses that each entry includes index, name, path, and active status. Since no annotations are provided, the description fully covers the behavioral aspects, including the critical detail that index is the handle for set_active_document.

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?

Two sentences, front-loaded with the main action, and each sentence adds necessary detail without redundancy. No wasted words.

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?

Despite no output schema, the description explains the content of each entry and cross-references sibling tools. It is fully adequate for understanding the tool's function and return structure.

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 no parameters, so by guidance baseline score is 4. The description correctly assumes no additional parameter info is needed.

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 tool enumerates open Cinema 4D documents, using specific verb 'Enumerate' and resource 'documents currently open'. It distinguishes from sibling tools like get_document_state and set_active_document.

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?

Explicitly provides when-to-use guidance: 'get_document_state only reports the active document; this is how you discover the others before switching.' It names the alternative tool and context.

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