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

With no annotations provided, the description carries the behavioral disclosure burden. It explicitly states that without auth it returns an 'honest config_needed stub' and that no data is invented, which is valuable anti-hallucination guidance. It does not cover result structure or error behavior beyond auth, preventing 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?

Three short sentences front-load the operation, then give a query example, then state the auth-failure behavior. Every sentence earns its place, and there is no filler or repetition of schema details.

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 description covers auth failure behavior well, but with no output schema it leaves the success return format, pagination, and body-snippet semantics open to inference. The low complexity of three optional parameters prevents this from being a larger gap, but it is still a clear omission.

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 baseline is 3, but the description adds a concrete Gmail query example ('newer_than:7d seller/order/refund') that demonstrates operator usage for the query parameter. This goes beyond the schema's simple 'Gmail query' description, though max_results and include_body receive no extra semantic guidance.

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 identifies the operation as 'Gmail search' with a specific resource (Gmail) and an example query format. It also distinguishes itself from siblings like gold_setup_check and gold_sheets_append by its search focus, so an agent can select it without ambiguity.

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 when to use the tool through 'Gmail search' and the query example, and the BYOK OAuth context suggests an authentication prerequisite. However, it does not explicitly mention alternatives or when not to use it, leaving some usage inference to the agent.

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

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

The description discloses that the tool only shows key names, never values, which is a meaningful behavioral constraint beyond what the empty schema and missing annotations provide. It also states the tool's output scope (license tier, key status, next step). However, it doesn't explicitly state whether the tool makes any external calls or is purely local, which would be useful but is not a major gap given the tool's simple nature.

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 two sentences with no wasted words. The imperative 'run this FIRST' is front-loaded, and the rest of the sentence packs in the resource, the output, and a privacy guarantee (names only, never values). Every clause 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?

For a zero-parameter setup check tool, the description is nearly complete. It tells the agent when to run it, what it will learn, and a key behavioral constraint. The only minor gap is that it doesn't describe the exact output format or whether the tool performs any side effects, but given the tool's simplicity and the absence of an output schema, the description carries enough weight to guide correct invocation.

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. The description adds context about what the tool checks and reports, which is valuable even though there are no parameters to document. The baseline for zero-parameter tools is 4, and the description meets that by explaining the tool's purpose and output.

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 verb ('run this FIRST') and resource ('SETUP CHECK for GSuite MCP Lane'), and clearly distinguishes its purpose from the sibling tools by framing it as a setup/readiness check rather than a search or append operation. It also names the exact resource being checked (license tier, API keys).

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 says 'run this FIRST', which is a clear usage directive. It also tells the agent what the tool will reveal (license tier, which API keys are set vs missing) and that it should be used before other operations, effectively routing the agent to this tool as a prerequisite step.

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

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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the authentication model (BYOK Google OAuth) and the 'No hosted sync' behavior, which is useful. However, it does not explain mutation effects, error behavior, response format, or what happens when values exceed the provided range.

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 short and front-loaded with the key operation and auth model. Minor redundancy exists between 'Append [[col1,col2]] to spreadsheetId' and the schema's values/spreadsheet_id fields, but the overall structure is efficient and readable.

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 schema covers all parameter details)Skip no output schema is provided, so response behavior is unexplained. The description gives the essential operation and auth/sync context, but lacks details about return values, error cases, rate limits, or how the optional range parameter behaves during append.

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 input schema already documents all four parameters with descriptions, so the baseline is 3. The description repeats spreadsheetId and the values array format but adds no new meaning beyond the schema, and it does not clarify the 'range' parameter or how it interacts with appending.

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 verb and resource ('append rows' to Google Sheets) and includes the value format [[col1,col2]]. It clearly identifies the core operation, though it does not explicitly contrast with sibling tools or state what it does not do (e.g., overwrite/update).

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?

There is no indication of when to use this tool versus alternatives, nor any mention of preconditions such as whether the spreadsheet must already exist or whether the BYOK OAuth scope needs specific permissions. The 'No hosted sync' comment hints at a limitation but is not framed as usage guidance.

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