ga4_property_get

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

Declares 'Read-only', which is key. Lists returned fields. No annotation support, but description is adequate. Missing error behavior (e.g., property not found) but acceptable for simple GET.

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?

One sentence plus 'Read-only.' Every word adds value. No 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 simple get with one parameter and no output schema, description covers purpose and main returned fields. Could specify response structure (e.g., returns a Property resource), but not critical.

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?

Single parameter 'property' is well-described in schema with example. Description adds no further semantics beyond schema coverage. 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?

Description clearly states 'Get a single GA4 property by ID' with specific fields listed (display name, time zone, etc.). Distinct from sibling tools like ga4_properties_list.

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?

Implicitly clear when to use (retrieve one property by ID), but no explicit guidance on when not to use or alternatives. Could mention to use ga4_properties_list for listing.

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