Save Blog Post

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

Annotations already indicate a non-read-only, idempotent, non-destructive operation. The description adds useful concrete behavior: local file storage, automatic filename generation from title/date, and directory fallback to BLOG_SAVE_DIRECTORY or ./posts. It does not mention overwrite behavior, but the idempotent hint reduces the need for that detail.

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 well-structured, front-loaded docstring: a one-sentence summary, a brief usage note, bullet-style Args, and a Returns block. Every sentence earns its place and there is no redundant content.

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 is simple, and the description covers the main workflow, directory defaults, and return values. However, it leaves ambiguity about whether task_id and content are mutually exclusive or if one is required, and the empty input schema makes the actual accepted parameters uncertain.

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?

The input schema declares zero properties, but the description compensates by documenting all four parameters (task_id, content, filename, directory) with concise explanations and defaults. This adds substantial meaning beyond the empty schema and is essential for correct invocation.

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 opens with 'Saves a blog post as a local markdown file,' a specific verb+resource pair. It also clarifies that the tool supports existing task IDs or direct content, clearly distinguishing it from siblings like blog_deploy_github and blog_get_status.

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 gives context about how to use the tool ('use existing task_id or directly enter content') and the default directory behavior, but it does not explicitly state when to prefer this over alternatives such as blog_finalize_draft or blog_deploy_github. Usage is implied rather than directly guided.

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