save_theme

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

With no annotations, the description must carry behavioral transparency. It discloses the default save location (~/.docx-mcp/themes/<name>.json), which is useful. However, it does not clarify whether existing files are overwritten, whether directories are created, or what errors occur, leaving behavioral 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 sentence that leads with the verb and resource, immediately stating the core purpose and default location. It contains no filler and is easy to parse.

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?

The tool has a nested `theme` object and an optional `output_path`, but the description ignores `output_path` and does not explain overwrite behavior or return values. The schema covers both parameters, which helps, but without annotations and output schema, a bit more context would be needed for fully confident use.

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 100%, so the baseline is 3. The description adds minimal parameter-related context beyond the schema (only that `name` determines the default path). It does not enrich understanding of `theme` or `output_path`, but the schema already documents them thoroughly.

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 a specific action ('Uloží šablonu') with a resource ('theme') and target format ('JSON soubor'), plus the purpose 'pro opakované použití' (for reuse). This distinguishes it from siblings like create_document, convert_markdown, and list_themes, which serve different functions.

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 phrase 'pro opakované použití' implies when to use the tool (persisting a theme for later), but it provides no explicit when-not-to-use guidance or alternatives. It does not mention list_themes as the complement for retrieving saved themes.

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