upload_confluence_attachment

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the base64 requirement but does not explain whether an upload replaces an existing attachment, whether permissions are needed, size limits, or what the outcome of a repeated upload is. For a mutating tool this is a notable gap.

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 two short, focused sentences with no filler. It front-loads the core action and includes the most critical invocation constraint, making it efficient and easy to parse.

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?

Although the schema fully documents parameters and the action is simple, the lack of annotations and output schema means the description should explain more about expected behavior, such as overwrite semantics, success response, or prerequisites. The current description is too sparse to fully guide an agent through edge cases.

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 100%, so all five parameters are already well documented. The description only reiterates the base64 encoding requirement already present in the schema, adding little beyond the structured definition.

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 a specific verb ('Upload'), resource ('file attachment to a Confluence page'), and required input format. It is unambiguous and differentiates itself from sibling tools like download_confluence_attachment and list_attachments_on_page.

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?

No guidance is provided about when to use this tool versus alternatives, such as checking existing attachments with list_attachments_on_page or downloading with download_confluence_attachment. The intended use is implied by the name but not explicitly supported with selection criteria.

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