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

Annotations flag it as non-read-only, non-idempotent, non-destructive, but the description adds real behavioral context the annotations lack: the link expires in a few minutes and must be opened by a HUMAN in a browser. It doesn't mention permission requirements or what happens on repeated calls, so it falls short of a 5.

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?

Four short sentences, front-loaded with the core action, followed by the expiry behavior and then the sibling disambiguation. Every sentence carries information the agent needs.

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?

With no output schema, the description correctly states what is returned (the OAuth URL) and adds the expiry and human-in-the-loop constraint. It is nearly complete for a two-parameter link-generation tool, missing only auth/permission expectations.

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 coverage is 50%: 'site' is described in the schema while 'provider' only carries an enum of 'gsc'. The description says 'for this site' but adds no meaning beyond the schema for either parameter, so the baseline of 3 for partial coverage is appropriate.

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?

States a specific verb and resource: returns the OAuth URL to connect Google Search Console. It also names the sibling tools for the other providers, so an agent can distinguish this from connect_bing and connect_platform without opening any 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?

Explicitly states when to use it (human opens the GSC OAuth link in a browser) and routes the alternatives: Bing uses connect_bing with an API key, and Shopify has no OAuth link, using connect_platform instead. Nothing is left to inference.

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