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

Annotations are sparse (readOnlyHint=false, destructiveHint=false, openWorldHint=true). The description adds meaningful behavioral context: it returns an MCP OAuth challenge for the host to open, and it includes a security guardrail about not asking for credentials. It does not fully explain the post-consent state change, but the OAuth initiation behavior is clear and not contradicted by 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?

Three short sentences, all substantive: the timing, the returned value, and a critical security constraint. The most important context is front-loaded. No filler or redundancy. Every sentence earns its place.

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 zero parameters and no output schema, the description covers the essential context: when to call it, what it returns, and a hard security rule. It might have benefited from explaining what happens after the OAuth flow completes, but the immediate next step (host opening the flow) is stated. Overall, an agent has enough to invoke it 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 tool has zero parameters, so the schema is trivially complete. With no parameters, the description does not need to explain parameter behavior. The baseline score of 4 for zero-parameter tools applies, and the description neither adds nor detracts in this dimension.

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 clearly states the tool's action: 'connect a CongressMCP account with OAuth' and specifically says it returns an OAuth challenge to open the authorization flow. It is unambiguously distinct from the sibling tools, which handle subscriptions and email signup steps. An agent can immediately understand this tool initiates the OAuth connection.

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 an explicit precondition: 'Use this after subscription activation when the user wants this chat to access CongressMCP.' It also provides a clear 'never' directive about not asking for secrets. However, it does not explicitly name alternative tools or state when NOT to use this one (e.g., before subscription activation), leaving that to inference from sibling names.

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