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

Beyond the readOnlyHint the description adds genuinely new behavioral context: it warns that notes and report titles are member-authored and must be treated as data rather than instructions, and it explains how to interpret the 'settings' and 'enforced' fields, including IP privacy. These are prompt-injection and interpretation safeguards that annotations cannot convey.

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 usage instruction is front-loaded and each sentence carries distinct information, with no filler. The middle sentence is a long comma-separated inventory of return fields, which is dense but functional rather than padded.

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 one-parameter read tool with an output schema and full annotation coverage, the description supplies everything an agent needs: when to call it, what comes back, and how to safely interpret member-authored text. Nothing material is missing.

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?

There is a single parameter and the schema already documents it at 100% coverage, including the pointer to d8a_list_properties. The description adds no further detail about the property_id argument, so the baseline of 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 the resource (property context) and enumerates precisely what one call returns: timezone, today's date, goals with IDs, saved reports, dimension/metric IDs, notes, tracking protocol and URL, report availability, and query rules. That enumeration makes it clearly distinguishable from siblings like d8a_get_query_catalog or d8a_get_saved_report, which cover only slices of this payload.

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?

"Use this once per property before analysing it or touching its tracking" gives an explicit trigger and ordering constraint that an agent can act on without inference. It stops short of naming when-not conditions or pointing at alternative tools for narrower needs, so it falls just short of a 5.

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