ga4_account_summaries

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is known. The description adds value by explaining what it returns (property IDs) and why that matters (for other tools), which is beyond the structured data. It doesn't mention pagination behavior, but with annotations covering safety and a simple list operation, the added context is sufficient.

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?

Two short sentences with no redundancy. The primary action is front-loaded, and the second sentence explains the tool's role in the broader toolset. Every word earns its place; there is no fluff or repetition.

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 list tool with a single optional parameter and a rich output schema (not described but available), the description covers the essential purpose and return-value significance. It does not explain pagination mechanics, but the schema covers the parameter and the description explicitly mentions returning all accessible accounts and properties. Minor gap: no mention of how many results or limits, but not critical for 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 single parameter page_token has 100% schema description coverage, so the schema fully documents it. The description does not add any parameter-specific detail, which is fine given the schema already explains the pagination token. Baseline 3 is appropriate because the schema does the heavy lifting.

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 ('List'), the resource ('every GA4 account and property'), and the access scope ('the authenticated user can access'). The second sentence explicitly frames it as the entry point for all GA4 work, which distinguishes it from sibling tools that operate on existing properties. This is very clear and actionable.

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 clearly indicates when to use this tool: as the starting point for any GA4 workflow, returning property IDs needed by other ga4_* tools. While it doesn't explicitly mention alternatives or when not to use it, the entry-point framing is so strong that an agent can infer it should be called first. It lacks explicit exclusions but the context is unambiguous.

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