confluence_upload_attachment

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

With no annotations at all, the description carries the full burden, and it uses that space well: it discloses the environment-variable gate, the mandatory confirm flag, and the significant fact that 'the file path is read by this local process' — a security-relevant behavior an agent cannot infer from the schema. It omits result/error behavior, but the critical behavioral traits of this gated mutation are surfaced.

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?

Two sentences, no filler: the action is front-loaded and the second sentence packs three high-value caveats. Every word earns its place.

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 description is complete about the gating and local-file behavior, but with no output schema and no parameter documentation, an agent must guess at the meaning of comment and max_chars and at what the call returns. Adequate for a 5-parameter gated mutation, but with clear gaps.

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 the description must compensate, but it only tacitly touches confirm and file_path. page_id (the attachment target), comment, and the oddly constrained max_chars (1000–50000) are left completely unexplained, so an agent cannot know what max_chars controls.

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?

States an unambiguous verb+resource pair: 'Upload a local file to a page.' The 'REST API v1' detail anchors it to a concrete implementation, and no sibling tool performs uploads, so differentiation from the read-oriented attachment tools (list_attachments, get_attachment) is inherent.

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 conveys availability preconditions ('Disabled unless CONFLUENCE_ALLOW_LOCAL_FILE_UPLOAD=true and confirm=true'), which tells an agent when the tool can fire, but it never states when to prefer this over an alternative or what to do when disabled. Usage context is implied rather than explicit.

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