save_draft

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

No annotations provided, so description carries full burden. It explains the append overwrite behavior and that it saves a Markdown draft. However, it doesn't mention permissions, file location, or whether it creates or overwrites by default, but the append hint mitigates this.

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?

Extremely concise: one sentence describing the action and one usage tip. No wasted words, front-loaded with the main action.

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 (3 parameters, 1 required), the description covers the core functionality and append use case. Output schema exists but is not shown; however, for a save tool, return values are likely straightforward. Could mention that it saves to a persistent location, but generally complete.

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 0%, so description must compensate. It explains the append parameter well, but content and filename (with default) are not described. The append explanation adds value, but other parameters lack detail.

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 verb 'Save' and the resource 'Markdown research draft'. It also distinguishes between saving and appending with append=True, which differentiates it from sibling tools like save_latex or save_report.

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?

Provides explicit guidance on when to use append=True ('for long-form papers so you never resend the whole accumulated draft'). Could be more specific about when not to use this tool versus alternatives like save_report, but enough for a simple tool.

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