snapshot_create

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

With no annotations provided, the description carries full burden for behavioral disclosure. While '创建快照' implies a write operation, it doesn't mention important behavioral aspects like whether this is a long-running operation, what permissions are required, whether it's idempotent, or what happens on failure. The parameter list provides some operational details but not comprehensive behavioral context.

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 well-structured with clear sections for purpose, parameters, and examples. It's appropriately sized with no redundant information. The only minor issue is that the purpose statement is extremely brief ('创建快照'), though this is culturally appropriate for Chinese documentation.

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 6-parameter mutation tool with no annotations and no output schema, the description provides adequate but incomplete coverage. It documents parameters well but lacks information about return values, error conditions, performance characteristics, and how this tool relates to other snapshot operations. The examples help but don't fully compensate for these gaps.

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?

With 0% schema description coverage, the description compensates well by listing all 6 parameters with brief explanations in Chinese. It clarifies that 'indices' is optional and defaults to backing up all indices when not provided, and explains the purpose of boolean flags like 'ignore_unavailable' and 'include_global_state'. The examples further illustrate parameter usage.

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's purpose as '创建快照' (create snapshot), which is a specific verb+resource combination. However, it doesn't differentiate from sibling tools like snapshot_clone, snapshot_delete, or snapshot_restore, which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites (like needing a repository first), when not to use it, or how it differs from related snapshot operations in the sibling tool list.

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