Begin source reauthentication

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does disclose key behavioral traits: the browser is visible and persistent, and the user manually completes GitHub, SAML, and MFA steps. However, it does not mention what happens after the browser opens, whether the tool waits, or what response/status is returned, leaving some behavioral ambiguity.

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, front-loaded sentence that efficiently conveys the core action and user involvement. No filler or redundant information; every clause adds meaningful detail.

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?

The tool is relatively simple (one param, no output schema), but the description omits critical contextual details: when to initiate reauth, what the sourceId parameter identifies, and what happens after the browser opens. This leaves the agent unclear about the tool's role in the broader authentication workflow.

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 0%, and the description does not mention the sourceId parameter at all. There is no explanation of what sourceId refers to or how it relates to the reauthentication flow. The description completely fails to compensate for the schema's lack of semantic detail, leaving the parameter's meaning only inferable from the tool name.

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: opens a visible, persistent local browser at the configured GitHub Pages URL for the user to complete reauthentication. It clearly implies the resource (source) and purpose (reauth), distinguishing it from sibling tools like get_source_auth_status or validate_source_auth, though it does not explicitly contrast them.

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 is provided on when to use this tool versus alternatives, such as when a source's auth has expired or when to call validate_source_auth first. It only describes the action, not the appropriate context or preconditions.

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