ga_list_properties

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

readOnlyHint already indicates a safe read operation, and the description adds the non-obvious behavior of aggregating properties across all accounts when no accountId is given. It does not describe return format or pagination, but annotations reduce the burden.

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, focused sentences convey the purpose and the key filtering behavior. The main action is front-loaded and every sentence earns its place with no redundant detail.

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 list operation with one optional parameter and a readOnly annotation, the description sufficiently explains the core behavior and account-scoping logic. No output schema exists, but 'list' clearly implies a list of properties as the return value.

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 schema already fully documents accountId with an example, giving a 100% coverage baseline of 3. The description adds meaningful context by stating the consequence of omitting the parameter, which is behavior not captured in the schema.

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 opens with 'List Google Analytics properties', using a specific verb and resource that distinguishes it from sibling tools like ga_list_accounts and ga_list_data_streams. The optional account ID filter adds scoping detail.

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?

It clearly explains when to use the optional accountId and what happens without it (aggregates across all accessible accounts). However, it does not explicitly mention when not to use this tool or name alternatives, so it stops short of full 5.

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