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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=false, and destructiveHint=false, covering the safety profile. The description adds no behavioral context beyond restating the purpose; it does not explain what the status check entails, whether authentication is required, or what a failed check looks like.

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 front-loaded sentence with zero wasted words. It communicates the action and resource immediately, which is appropriate for a simple status-check tool.

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 simple read-only status tool with one required parameter and rich annotations, the description covers the essential invocation context. However, since there is no output schema, it could clarify what 'status' returns (e.g., connected/disconnected, error details), leaving a minor gap.

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?

With 100% schema description coverage, the single site_id parameter is fully documented in the input schema. The description's phrase 'for a site' loosely maps to site_id but adds no format, syntax, or constraints beyond what the schema already provides, so the baseline of 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 states a specific verb ('Check') and resource ('Google Analytics connection status'), making the tool's core function clear. It implicitly distinguishes itself from siblings like connect_ga (which establishes a connection) and get_ga_metrics (which retrieves metrics), but does not explicitly name or contrast with them.

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 explicit guidance on when to use this tool versus alternatives such as get_ga_metrics or connect_ga, nor does it state prerequisites like needing a connected Google Analytics account. Usage is only implied by the tool name and the phrase 'for a site'.

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