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

With no annotations, the description carries the full burden. It discloses that this is a read-only listing scoped to readable properties and enumerates the returned fields, which is useful, but it says nothing about pagination, rate limits, or auth failures.

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 tight sentences with zero waste: the purpose and returned fields come first, the routing instruction second. 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 simple discovery tool with no output schema and one optional parameter, the description covers purpose, returned fields, and the downstream step an agent needs. Minor gaps in pagination/auth behavior remain, but nothing essential is missing.

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 account parameter is fully documented in the schema (100% coverage), where the 'read as' semantics and multi-account caveat live. The description adds nothing about the parameter beyond what the schema provides, so the baseline 3 applies.

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"), resource (GA4 properties), and scope ("the connected Google account can read"), plus the exact fields returned (property id, name, account). It is trivially distinguishable from the sibling ga4_report, which is named as the follow-up consumer.

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?

"Pass the id to ga4_report" gives explicit workflow guidance, positioning this as the discovery step before reporting. It does not state exclusions or when an agent should skip this tool, so it stops short of full when/when-not coverage.

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