get_property_schema

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

The description adds a critical behavioral detail beyond the readOnlyHint annotation: the returned object can be very large (10k+ tokens). This is significant context for an agent choosing whether to invoke the tool.

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 extremely concise at two sentences. The first sentence states the core purpose, and the second adds usage guidance and a warning. Every sentence adds value.

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?

The description is largely complete given the tool's simplicity (no parameters, read-only). It covers purpose, size warning, and alternative. However, it omits the format of the returned schema (e.g., JSON structure), which could be helpful if an agent needs to parse the output, but this is a minor gap.

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?

Since there are no parameters, the description does not need to explain parameter meaning. A score of 4 is baseline for zero-parameter tools, as no additional detail is required.

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 uses a specific verb ('Returns') and resource ('complete schema for the configured GA4 property'), clearly stating what the tool does. It distinguishes from the sibling tool 'search_schema' by noting the scope (complete vs. most discovery tasks).

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 explicitly advises to use 'search_schema for most discovery tasks' and warns about the large response size (10k+ tokens). This provides clear guidance on when to use this tool and when to use an alternative.

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