get_property_configuration

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

Annotations already declare readOnly/idempotent/openWorld, and the description adds real behavioral context on top: per-section pagination via data.nextPageToken, the 1–200 page_size bound, which sections are singletons, and the critical warning that a denied/unavailable section is not an empty list. That last point directly prevents a wrong inference from the output, which is exactly what the description should carry.

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?

Front-loaded with the core action and every subsequent line adds a distinct operational fact. The phrasing is telegraphic in places ('List sections return data.nextPageToken'), which is dense but not wasteful.

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?

An output schema exists, so return values needn't be explained, and the description still supplies the pagination contract and the partial/denied-section caveat an agent needs to interpret results. What's missing is any explanation of the account and property_id targeting parameters, which matters for a multi-property API.

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 description coverage is 0%, so the description must compensate; it does so for page_tokens ('keyed by section name'), page_size ('1–200'), and partially for sections (key_events, attribution, data_retention called out). However, account and property_id are never explained, and four of the seven section enum values get no semantic coverage, so compensation is only partial.

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 a specific verb+resource ('read only requested configuration sections') plus the return shape (individual statuses, partial flag). It distinguishes the key_events section from get_events by name, though it does not distinguish itself from get_property/get_metadata, which are the closest siblings in scope.

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?

Gives a clear routing rule for the key_events section ('compare with get_events') and per-section usage constraints (attribution/data_retention are singletons, no page tokens). It lacks explicit when-not-to-use guidance relative to get_property or get_metadata, so it falls short of a full 5.

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