atlassian-browser-mcp

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

The description adds valuable behavioral context beyond the destructiveHint annotation: it explains that files with the same names create new versions automatically, describes the batch nature of the operation, and mentions that all files share the same comment/minor_edit settings. However, it doesn't mention rate limits or authentication requirements.

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 well-structured with clear sections: purpose statement, efficiency comparison, behavioral note, usage scenarios, and parameter summary. Every sentence adds value, and the information is front-loaded with the most important details first.

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?

Given the destructiveHint annotation, 100% schema coverage, and presence of an output schema, the description provides excellent contextual completeness. It covers purpose, differentiation from siblings, behavioral nuances, and usage scenarios, making it fully adequate for this mutation tool.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description's 'Args' section mostly repeats schema information, though it adds minor context about the JSON return format. This meets the baseline for high schema coverage.

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 the specific action ('upload multiple attachments') and target resource ('Confluence content'), distinguishing it from the sibling 'confluence_upload_attachment' by emphasizing bulk efficiency and automatic versioning. It explicitly contrasts with the single-file alternative.

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 provides explicit guidance on when to use this tool ('more efficient than calling upload_attachment multiple times') and includes a 'Useful for' section with three concrete scenarios. It clearly differentiates from the single-file sibling tool.

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