atlassian-browser-mcp

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

Annotations provide destructiveHint=true, indicating this is a write operation. The description adds valuable context beyond annotations: it mentions read-only mode constraints, Jira client availability requirements, and JSON validation errors. However, it doesn't disclose rate limits, batch size limits, or atomicity behavior (whether all-or-nothing).

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 (Args, Returns, Raises) and front-loaded purpose statement. However, the Args section repeats parameter names without adding value beyond what's in the schema, making it slightly verbose. The core information is efficiently presented in the first sentence.

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 destructive batch operation with rich schema coverage and output schema, the description is reasonably complete. It covers the core purpose, parameters, returns, and error conditions. However, it lacks details about batch behavior (size limits, atomicity) and doesn't mention authentication requirements or rate limits, which would be helpful given the destructive nature.

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 input schema thoroughly documents both parameters. The description adds minimal value beyond the schema, only briefly mentioning the parameters in the Args section without providing additional semantic context. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Create multiple Jira issues in a batch') and resource ('Jira issues'), distinguishing it from the sibling 'jira_create_issue' tool which handles single issue creation. The title reinforces this distinction with 'Batch Create Issues'.

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 clear context for when to use this tool (creating multiple issues at once) versus the single-issue alternative, but doesn't explicitly state when NOT to use it (e.g., for single issues) or mention other batch alternatives like 'jira_batch_create_versions'. The validation-only mode is mentioned but not contrasted with regular creation.

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