save_config

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

The description discloses a key behavior (automatic backup creation), which is critical for understanding the tool's side effects. However, it does not mention other important behaviors like overwriting existing files, error handling, or permission requirements. With no annotations, the description carries full burden and leaves gaps.

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 single, well-constructed sentence that front-loads the core action. Every word is necessary; no extraneous information.

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's simplicity (2 params, no output schema) and the presence of sibling tools that clarify the ecosystem, the description covers the essential purpose and key behavior. It could be slightly improved by noting the backup location or naming convention, but it is largely sufficient.

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?

Input schema has 100% description coverage for both parameters ('path' and 'config'), so the schema already provides adequate meaning. The description adds no additional parameter-level detail beyond what the schema states.

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 primary action ('Saves the configuration JSON') and explicitly mentions an important side-effect (automatic timestamped backup). This distinctly differentiates it from sibling tools like get_config (read), list_backups (list), restore_backup (restore), and validate_command (validate).

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 implies the tool is for saving configuration, but does not explicitly state when to use it versus alternatives, nor does it provide any conditions or prerequisites. Usage context is only implied by the action itself.

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