file_document

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

No annotations are present, so the description carries full burden. It mentions creating a 'referential containment relationship' and returns either relationship ID or ToolError, but does not disclose permissions, idempotency, or whether the document/folder must exist beforehand.

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 front-loaded with the action, but includes a docstring-style parameter table and returns section. Could be condensed; the parameter info could be integrated into the prose.

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?

The tool has 2 simple parameters and an output schema. The description covers basic purpose and return value, but omits context like error conditions, required existence of referenced objects, or any side effects.

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%, but the description provides clear parameter explanations (document_id_or_path as unique identifier or path). It adds meaning beyond the bare schema, though it does not elaborate on format or validation.

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 'files a document to a folder', which is a specific verb+resource. It distinguishes itself from sibling tools like 'unfile_document' (opposite) and 'create_document' (creates a document, not filing).

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 is provided on when to use this tool versus alternatives such as 'create_document' or 'unfile_document'. The description lacks any context about prerequisites (e.g., document must already exist) or why you'd choose this tool.

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