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

With all annotations false, the description carries the behavioral burden. It discloses the browser handoff behavior, the need to keep requestId and pollSecret private, and the prohibition on asking for credentials in chat. This adds meaningful operational context beyond the 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 three short, purposeful sentences. It front-loads the core purpose, then immediately gives security-critical handling instructions. Every sentence earns its place and no content is redundant with the empty schema.

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 parameterless tool with no output schema, the description explains what the tool does, when it is needed, and how the agent should handle the returned values. Minor gap: it does not explicitly instruct calling finish_sign_in after the handoff, but this is arguably implied by the sibling tool and overall flow.

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 tool has zero parameters, so the schema provides no semantic burden. The description correctly focuses on the tool's action and output handling instead of parameters, which is appropriate for a parameterless tool.

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 uses a specific verb ('Start the browser handoff') and resource ('Noemic sign-in'), and it clearly states the purpose: enabling personalized network reads or saving an unpublished wager draft. It also distinguishes itself from the sibling finish_sign_in by describing the initial step of the flow.

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 explicitly states when to use the tool: before personalized network reads or saving an unpublished wager draft. It also gives clear handling instructions (show only signInUrl, keep secrets private, never ask for credentials), though it does not explicitly name finish_sign_in as the follow-up tool.

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