Save Markdown

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

No annotations are provided, so the description carries full burden. It discloses force-write behavior (last-writer-wins), auto-creation of folders, and optional image upload with placeholder replacement. These are key behavioral traits beyond basic mutation.

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?

Two sentences, zero waste. First sentence states the core action and key features (auto-create folders, optional images). Second sentence adds the force-write note and role. Information is front-loaded and every part earns its place.

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 4 parameters, no output schema, and no annotations, the description covers the main workflow, important behaviors, and roles. It lacks error handling or return value info but is adequate for an agent using a write tool with clear side effects.

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 4 parameters (coverage 100%) with detailed descriptions. The description adds high-level context about the workflow (image upload before saving) but does not significantly add meaning to individual parameters beyond what the schema provides.

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 it saves (creates or overwrites) a .md file by path, with folder auto-creation and optional image upload. It distinguishes itself from sibling tools like append_to_markdown by calling itself 'the headline agent tool' for writing.

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?

While not explicitly saying when not to use, the description positions this as the primary write tool ('headline agent tool') and mentions it's a force-write. The sibling update_markdown exists but the name 'save' implies create/overwrite, giving implicit guidance. Missing explicit comparison to alternatives.

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