add_attachment_tool

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

No annotations are provided, so this description carries the full burden. It discloses that this is a write operation from base64 content, but does not state overwrite semantics, path constraints, directory creation, accepted base64 format, or any side effects; the dangling 'data: {size_bytes, mime_type}' fragment does not clarify behavior.

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 first sentence is concise and front-loaded, but the second fragment 'data: {size_bytes, mime_type}.' is unstructured and unclear; it does not earn its place and may be mistaken for a parameter or output specification without explanation.

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?

With no annotations and no parameter descriptions, the definition is incomplete for a write tool. The core idea is present, but an agent is left guessing about overwrite behavior, target path semantics, optional vault use, and the intended meaning of the data fragment. The presence of an output schema reduces the need for return-value detail, but not the need for behavioral and path guidance.

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%, and the description only hints at content_base64 via 'base64-encoded content.' The required path and optional vault parameters receive no semantic explanation, and size_bytes/mime_type appear nowhere in the schema, making the second line unhelpful for parameter understanding.

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 names a specific action and resource: 'Write a binary attachment (image, PDF, etc.) to the vault', and clarifies the input encoding. While it doesn't explicitly compare itself to sibling attachment tools like create_attachment_token_tool, the write-versus-list/read/token distinction is largely clear.

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?

Usage is implied: use this when you need to persist binary content into the vault. There is no explicit guidance about when to choose write_note_tool for text, create_attachment_token_tool for tokens, or how path/vault should be selected, so the agent must infer routing.

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