capabilities

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions what is shown ('enabled connectors, defaults, and key analysis thresholds') but does not describe traits like read-only status, potential rate limits, authentication needs, or output format. For a tool with no annotations, this is a significant gap in transparency.

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, efficient sentence: 'Show enabled connectors, defaults, and key analysis thresholds.' It is front-loaded with the core purpose, has zero waste, and is appropriately sized for a no-parameter tool, making it highly concise and well-structured.

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 the tool's complexity (simple, no parameters) and the presence of an output schema, the description is minimally complete. It states what is shown but lacks behavioral context (e.g., read-only nature, which is implied but not explicit). With an output schema, it need not explain return values, but for a tool with no annotations, more disclosure would improve completeness.

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 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description does not add parameter semantics, but with no parameters, the baseline is 4 as it adequately addresses the lack of inputs without unnecessary detail.

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 purpose: 'Show enabled connectors, defaults, and key analysis thresholds.' It uses specific verbs ('show') and resources ('connectors, defaults, thresholds'), making the function evident. However, it does not explicitly distinguish this tool from its sibling tools (e.g., analytics or GSC tools), which slightly reduces clarity in context.

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 provides no guidance on when to use this tool versus alternatives. It lacks context on prerequisites, timing, or comparisons to sibling tools (e.g., analytics_data_quality_report or gsc_list_sites), leaving the agent without usage direction beyond the basic purpose.

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