atlassian-browser-mcp

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

The annotations already declare 'destructiveHint: true', so the agent knows this is a destructive operation. The description adds minimal behavioral context by stating it deletes a page and mentions error conditions (client not configured), but doesn't elaborate on irreversible effects or permissions required beyond annotations.

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. However, the Args section is redundant with the schema, and the Raises section could be more concise, slightly reducing efficiency.

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 tool's complexity (destructive operation), annotations cover safety, and an output schema exists (implied by 'Returns'), the description is mostly complete. It lacks usage guidelines and deeper behavioral details, but covers purpose and basic error handling adequately.

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%, with the parameter 'page_id' fully documented in the schema. The description repeats this information in the Args section but doesn't add meaningful semantics beyond what the schema provides, such as format examples or sourcing guidance.

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 ('Delete') and resource ('an existing Confluence page'), distinguishing it from sibling tools like 'confluence_create_page' or 'confluence_update_page'. It precisely defines what the tool does without ambiguity.

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 no guidance on when to use this tool versus alternatives like 'confluence_move_page' or 'confluence_update_page', nor does it mention prerequisites (e.g., needing page ID from 'confluence_get_page'). It lacks context for decision-making.

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