save_block

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

With no annotations, the description must disclose behavior itself; it only states the save action and parameter meanings. It does not mention side effects such as overwriting existing files, file permissions/limitations, or what happens if there is no selected block, which is critical for a mutating operation.

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 definition is compact: one clear summary sentence followed by a concise argument list with no filler. Important details like format examples are included without bloating the text.

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?

For a four-parameter tool with no annotations, the parameter explanations are solid and return values are covered by the output schema. However, the definition lacks guidance on choosing this tool among many sibling save/export tools and omits behavioral caveats such as overwrite behavior, so an agent is not fully oriented.

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 has no property descriptions (0% coverage), and the description compensates by explaining all four parameters: doc_id provenance, filename as output path, format with concrete examples, and argument as optional/format-specific. This is essential semantic information the schema alone does not provide.

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 opening line 'Save selected block to a file' uses a specific verb and resource, clearly indicating the operation. It is understandable on its own, but it does not explicitly distinguish itself from sibling save/export tools such as save_document, save_document_as, or export_page_as_image.

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 implies use after open_document via 'doc_id: Document ID from open_document' and implies the tool targets a current selection ('selected block'). However, it gives no explicit when-to-use/when-not-to-use guidance or alternatives for saving whole documents or exporting pages/images.

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