svn_propset

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

No annotations are provided, so the description must disclose behavioral traits. The term 'Guarded' hints at a safety feature, but it is not explained. The presence of the 'riskAck' parameter is not mentioned, and the description does not clarify what happens if it is false or other constraints. The description fails to provide sufficient transparency about the tool's behavior.

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 very concise at 7 words, but it sacrifices essential details. While it is front-loaded with the key action 'propset', the brevity leads to ambiguity. Every sentence should add value, and here the single sentence is too minimal to be fully effective.

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 tool has 5 parameters (3 required), no annotations, and no output schema, the description is severely lacking. It does not explain the 'guarded' concept, the required 'riskAck' field, or what the tool returns. The description is inadequate for an AI agent to understand the tool's full context and usage.

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?

The schema has 5 parameters with only 40% description coverage (cwd and paths have descriptions). The tool description adds no information about any parameters, failing to compensate for the low coverage. Parameters like 'riskAck' remain completely unexplained, making it difficult for an AI agent to use the tool correctly.

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 states it's an svn propset for a working copy, which clearly identifies the verb and resource. However, the term 'Guarded' is vague and does not fully distinguish from sibling tools like svn_propset_eol_style. The description lacks specificity about what makes this tool different from other propset-related tools.

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?

The description only mentions 'explicit paths' as a constraint, but provides no guidance on when to use this tool versus alternatives like svn_propset_eol_style. There is no mention of prerequisites, exclusions, or context where other tools would be preferred.

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