atlassian-browser-mcp

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

Annotations declare readOnlyHint=true, indicating a safe read operation, which the description aligns with by using 'Get'. The description adds minimal behavioral context beyond annotations—it specifies 'all components' but doesn't mention pagination, rate limits, or authentication needs. With annotations covering safety, this is adequate but not rich in additional details.

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 a single, clear sentence with zero wasted words. It's front-loaded with the core action and resource, making it highly efficient and easy to parse for an AI agent.

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 low complexity (one parameter, read-only operation), annotations covering safety, and an output schema present (which handles return values), the description is reasonably complete. It states what the tool does, though it lacks usage guidelines. For a simple retrieval tool, this is mostly sufficient.

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 'project_key' fully documented in the schema (including description, pattern, and type). The description adds no extra parameter details beyond implying it's for a 'specific Jira project', which is already clear from the schema. Baseline 3 is appropriate as 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 action ('Get all components') and resource ('for a specific Jira project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate from sibling tools like 'jira_get_project_issues' or 'jira_get_project_versions', which also retrieve project-related data, so it doesn't reach the highest score.

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. For example, it doesn't mention if this is for listing components versus other project details, or if there are prerequisites like needing the project key. This leaves the agent without context for tool selection among siblings.

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