configure_design_system_source

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

The description states that this saves a source-file configuration, which adds some context about persistence. However, it does not mention that this overwrites an existing configured source or how the change affects future inventory/diff operations; the destructiveHint annotation is carrying most of the risk disclosure.

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 single sentence is short, front-loaded with the action verb, and clearly communicates the central purpose. It loses little from being more structured, example, or explaining the .raven config location.

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?

With 5 parameters, a nested object, and no output schema, the description is rather minimal. The schema fills most knowledge gaps, but the description would benefit from noting the persistent/overwriting nature of the action, any required environment ordering (for example ensuring DESIGN.md exists), or how aliases relate to the source file.

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 coverage is 100%, so the schema fully documents project_dir, source_kind, platform, aliases, and design_file_path. The description only adds the fact that the design file is local and used for inventory/comparison, which contributes little 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 clearly states the action ('Save') and the target resource (the local DESIGN.md file Raven should use), and it connects to the tool's inventory/comparison purpose. It differentiates the tool from generic read/update operations but does not explicitly distinguish it from sibling configuration-like tools such as update_design_md.

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 intent of using this during setup for design-system inventory/comparison is implied, but there is no explicit 'use this when' guidance, no exclusion for editing/reading DESIGN.md, and no comparison to alternatives like update_design_md or read_design_md.

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