buzz_login

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

With no annotations, the description carries the full burden, and it does exceptionally well. It discloses that the tool is NON-BLOCKING, returns immediately with a browser URL, attempts to open the browser, requires a follow-up call to confirm, and is idempotent. These are exactly the behavioral traits an agent needs to avoid misinterpreting the response.

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 dense yet tightly organized: purpose first, then usage context, then the non-blocking flow, then idempotency, then the parameter. Every sentence earns its place and there is no filler.

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 an OAuth login tool with no annotations and no output schema, this is complete: it explains the target audience, the two-step flow, how to confirm success, idempotency, and the optional parameter. An agent has everything needed to invoke and sequence this tool correctly.

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?

The schema already documents client_id and its env fallback with 100% coverage, so the baseline is 3. The description repeats the optionality and fallback but adds no new semantic detail beyond what the schema provides.

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 verb and resource: 'Sign in as YOURSELF for "post as me" (Ekam wire-sign OAuth)'. It also clearly distinguishes this login flow from the CLI alternative and from verification via buzz_whoami, so an agent can identify its purpose even without opening the schema.

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?

It explicitly says when to use this tool: for GUI/desktop clients that cannot run the buzz-mcp-login CLI. It also gives the full usage sequence: first call returns a URL, user approves, then call buzz_login again or buzz_whoami to confirm, plus the idempotent behavior. This is strong when-to-use and how-to-use guidance.

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