eds_da_move_source

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

With no annotations provided, the description carries the full burden. It mentions the token requirement but does not disclose side effects such as whether the source is removed, what happens if the destination already exists, or if the operation is reversible. The verb 'move' implies side effects but lacks explicit detail.

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 two sentences, front-loaded with the primary purpose and followed by the required token. It is concise with no fluff, every sentence contributes directly to understanding the tool.

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 two-parameter move operation, the description provides purpose and auth but omits critical behavioral context such as conflict handling, return values, or failure modes. Given the lack of output schema and annotations, the description leaves some gaps, but the core invocation is adequately covered.

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 coverage is 100% with both parameters described clearly ('Source DA document path' and 'Destination DA document path'). The description adds no additional parameter-level meaning beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb 'Move (rename)' with a clear resource ('authored source document') and scope ('to another path in Document Authoring'). It distinguishes from sibling tools like copy, delete, and put by indicating relocation rather than duplication or creation.

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 explicit guidance on when to use this tool versus alternatives like eds_da_copy_source or eds_da_delete_source. The auth token requirement is a prerequisite, not a usage guideline, and the description does not mention when a move is preferred over copy or delete.

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