atlassian_login

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

Description discloses that the tool launches a visible browser and waits for manual login, which is key behavioral info. However, it does not mention timeout, failure handling, or what happens after login. No annotations are present, so description carries full burden.

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?

One sentence, no wasted words. Action and purpose are immediately clear.

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 output schema presence and 2 parameters, description is too sparse. It lacks parameter explanations and return value info (output schema exists but not described). For a login tool that is a prerequisite, more context on usage flow is needed.

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?

Input schema has 2 parameters with 0% description coverage. Description does not explain parameters at all (target, url). It adds no meaning beyond the schema. Agent cannot infer how to use parameters from description.

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?

Description clearly states the tool launches a visible browser and waits for manual SSO/MFA login. The verb 'launch' and resource 'browser for login' are specific. It distinguishes from siblings which are all Confluence/Jira operations.

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?

No guidance on when to use this tool versus alternatives. Does not mention prerequisites, when not to use, or any usage context. Description is purely functional.

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