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

The description discloses that this tool starts an interactive browser flow and returns a URL requiring manual follow-up. Annotations already indicate a non-read-only, non-idempotent operation, and the description adds the important detail that the agent must open the URL and that user interaction is required.

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?

Two sentences convey the action, the returned artifact, the required user steps, and the next tool call with no filler. It is front-loaded with the core action and ends with an actionable directive.

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 login-flow starter with one optional parameter, an output schema, and clear annotations, the description covers the full workflow: what the tool does, what to do with its result, and what to call next. Nothing essential is missing.

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%: the only parameter, client_name, is already described as an optional string shown in Leafwright. The description adds no further parameter-specific meaning, so the baseline of 3 applies.

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 states a specific action ('Start a browser login flow') tied to a clear resource ('Leafwright MCP'). It also names the follow-up tool, leafwright_auth_status, which distinguishes it from sibling tools by signaling the beginning of the auth lifecycle.

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 gives clear sequential instructions: open the returned URL, choose an organization and project, then call leafwright_auth_status. It does not explicitly contrast this tool with leafwright_logout, but the intended workflow and next step are unambiguous.

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