svn_export

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

With no annotations, the description must disclose behavior. It fails to mention that svn_export creates a clean copy without .svn directories, or that it can operate on URLs or working copies. The only statement is a reiteration of the command name.

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 maximally concise at five words, but it sacrifices necessary detail. It is front-loaded in the sense of being short, but it fails to earn its place by providing value beyond the name.

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 4-parameter input with low schema coverage, no output schema, and a large sibling set, the description is far from complete. It does not help an agent understand how to invoke the tool correctly or what to expect from the output.

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 only 25% (only cwd has a description). The description does not explain src, dest, or revision parameters. Critical information about what these parameters represent (e.g., source path/URL, destination path) is missing.

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 'Run explicit svn export' clearly identifies the verb (export) and resource (svn). It distinguishes from siblings like svn_checkout or svn_add due to the specific SVN command naming. However, it assumes familiarity with 'svn export' and does not elaborate on the operation.

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. The sibling list includes many svn_* commands, but the description gives no context for choosing svn_export over, e.g., svn_checkout or svn_import.

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