Write VNyan settings.json

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

With no annotations, the description fully discloses behavior: requires closed VNyan due to triple-write, backs up file, refuses unknown and dedicated-tool keys, and notes flat namespace. Does not detail return value or error handling, but that is acceptable given no output schema.

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 well-structured paragraph with front-loaded action, followed by warnings, prerequisites, and usage tips. Every sentence adds value without redundancy.

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 simple parameter structure and no output schema, the description provides sufficient context for an agent to use correctly: what it does, prerequisites, safety measures, and how to find keys. Minor omission: doesn't explicitly state that the file is modified on disk, but 'source: disk' implies that.

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 covers all parameter semantics with 100% coverage. Description adds context about the key namespace (flat, ~279 keys) and provides guidance on how to discover valid keys, which goes beyond the schema.

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 uses a specific verb 'patches' and resource 'settings.json', and distinguishes from sibling tools by noting that certain keys have dedicated tools (props, colliders, etc.). Also clearly differentiates from vnyan_settings_get which is for reading.

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?

Explicitly states the prerequisite that VNyan must be closed, warns about silent overwrite, and recommends calling vnyan_settings_get first to see current values or vnyan_guide for key index. Also tells which keys to avoid (dedicated-tool keys) and directs to those tools instead.

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