save_sprite

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

With no annotations, the description carries the full burden: it does not disclose overwrite semantics, the optimistic-concurrency role of expected_revision, whether unsaved changes are flushed, or what errors occur on revision mismatch. Only the path requirement for unnamed documents is surfaced.

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?

A single front-loaded sentence with no filler; the path condition is placed immediately after the main action. Brevity here borders on under-specification rather than padding.

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?

A mutation tool with six parameters, no annotations and no output schema needs substantially more disclosure than this. Key behaviors an agent must know to call it safely — overwrite risk, revision-conflict handling, return value — are absent.

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 0% across 6 parameters, and the description only illuminates one of them (path for unnamed documents). overwrite, expected_revision, request_id, session_id and document_id remain entirely undocumented, so the description fails to compensate for the coverage gap.

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?

States a specific verb and resource ("显式保存文档" – explicitly save the document), and the qualifier distinguishes it from implicit/auto-saving. It is clear enough to separate from create_sprite, though the object is called a 'document' here while the tool is save_sprite.

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?

Gives one conditional rule (unnamed documents must specify a path), which is useful, but says nothing about when to prefer this over apply_operations or whether saving is needed after edits. Usage is only implied.

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