svn_move

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

No annotations provided. The term 'guarded' is vague – does it mean validation, rollback, or something else? There is no disclosure about handling conflicts, whether the source is deleted, or what constitutes a 'guard'. The parent directory creation is mentioned but not detailed.

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 a single short sentence, which is concise but under-specified. It omits critical details like parameter behavior, error states, and examples. The brevity comes at the cost of clarity.

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?

Given the lack of output schema, low schema coverage, and missing usage guidelines, the description fails to provide enough context for an agent to use the tool correctly. The tool has 3 parameters with 2 required, but the description only hints at the move behavior without covering the parameters or return values.

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 only 33%, with only 'cwd' having a description. 'src' and 'dest' lack descriptions. The description adds that parent directories are created for the destination, which provides some meaning, but the missing descriptions for src and dest make it difficult to understand required formats (e.g., should they be absolute or relative? Are they file paths or URLs?).

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 'Guarded working-copy svn move with parent directory creation' clearly indicates it performs an SVN move with extra safety and parent directory creation. However, it does not differentiate from sibling tools like svn_rename or svn_copy, which could be similar.

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 svn_rename, svn_copy, or svn_revert. The description implies a guarded move but lacks context on prerequisites or conditions for use.

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