ga4_get_property

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context: the id must be sourced from another call first, and it enumerates what the read returns in the absence of an output schema. It stops short of noting auth/scope requirements or staleness of the returned values.

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 sentences, front-loaded with the operation and its return fields, followed by the routing/prerequisite advice. Every clause carries information and no filler is present.

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 single-parameter read with no output schema, the description is complete: it enumerates the returned fields, defines the use case, and points to the sibling calls needed before and after. An agent can select and invoke this tool correctly from the description alone.

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?

Schema coverage is 100% and the single property_id parameter is already documented with accepted formats ("123456" or "properties/123456"). The description adds no further syntax, defaults, or format guidance 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?

The description names a specific verb (read) and resource (one GA4 property) and enumerates the exact configuration fields returned (display name, timezone, currency, industry, parent account). This cleanly distinguishes it from ga4_list_properties (plural listing) and ga4_get_data_stream (different resource) without opening any schema.

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 states exactly when to use it ("when the user asks how a known property is configured") and supplies both a prerequisite (call ga4_list_properties to obtain the id) and a routing rule (use ga4_list_data_streams for streams). Nothing is left to inference.

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