ga4_get_property_details

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

Annotations already declare readOnlyHint=true, so no safety concerns are hidden. The description adds behavioral transparency by enumerating the returned metadata fields and explicitly accepting both numeric and resource ID formats, which goes beyond the bare schema.

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 front-loaded with the core purpose, followed by a compact return-field list and the parameter format note. Every sentence adds useful information without redundancy.

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-property read tool with a read-only annotation and an available output schema, the description covers the purpose, return content, and accepted input formats. Sibling tools are clearly distinct from this focused metadata operation, so no additional disambiguation is needed.

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 input schema only says property_id is a string, with no description. The tool description compensates by explaining that property_id can be either a numeric string or a full resource name, with concrete examples, giving the agent the needed format guidance.

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 'Full metadata for a single GA4 property' with a clear resource and scope, and lists the exact fields returned. This distinguishes it from sibling list/report tools, which target multiple items or aggregated metrics.

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 implies this is for retrieving metadata about one property, and the singular scope separates it from list tools. However, it does not explicitly state when to prefer this over alternatives or mention any exclusions, leaving usage guidance mostly implicit.

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