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

Annotations set readOnlyHint=false, openWorldHint=true, etc., but the description adds crucial behavioral detail: it is a read-only consent flow despite the mutation hint, requires a browser redirect, has a five-minute expiry, single-use callback, and binding to account and site. These are essential operational traits not covered by annotations, making this highly transparent.

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 series of six short sentences that front-load the critical action ('Start read-only Google consent') and then provide necessary constraints. It is efficient with no obvious redundancy, though it could be slightly more structured by grouping prerequisites and constraints.

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 no output schema and annotations that only signal open-world, non-idempotent, non-destructive behavior, the description adequately covers the consent flow's required steps and temporal constraints. It could benefit from mentioning what happens after consent (e.g., connection saved) or error conditions, but it is largely complete for an agent to invoke 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?

Schema coverage is 100%, so the schema already documents parameters (id, property, language). The description mentions 'account' and 'site', which loosely correspond to id and property, but adds no syntax, format, or meaning beyond what the schema provides. Baseline 3 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?

The description opens with 'Start read-only Google consent', which indicates the operation begins a consent flow for Google Search Console. However, it does not explicitly name the resource being connected (Search Console) or the resulting action (connecting a property), making it less distinct from siblings like 'disconnect_search_console' or 'sync_search_console'. The purpose is implied but lacks the specific verb+resource precision needed for a 4 or 5.

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 implies usage by stating prerequisites (account owner must follow redirect) and constraints (consent expires, callback single-use), but it does not explicitly say when to use this tool versus alternatives like 'sync_search_console' or 'disconnect_search_console'. The guidance is inferable from context but not clearly delineated.

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