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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real substance beyond them: what each value bucket means, that resolution rules may be set or limited by account/organization rules, and the non-obvious caveat that applied.excluded_url_params also lists built_in_excluded_url_params which always apply and are never saved.

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 core instruction is front-loaded and every clause carries information. The final sentence about built_in_excluded_url_params is dense and slightly run-on, but it is a genuinely useful edge-case warning rather than filler.

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?

With an output schema present and annotations covering safety, the description only needs to explain the semantics of the returned buckets and the rule for acting on them, which it does. It omits error behavior (e.g., unknown property_id) and whether a partial read is possible, which are minor given the read-only, single-parameter shape.

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 (property_id) with 100% schema coverage, so the schema already carries its meaning. The description adds nothing about the parameter itself; baseline 3 applies when the schema does the work.

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 and resource ("Read a property's complete editable settings") plus the timing constraint ("before preparing a change"), and decomposes the result into own/applied/resolution. This distinguishes it from the sibling get_property_context (read-only overview) and from prepare_property_settings_change (the mutating step).

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 clear when-to-use guidance ("before preparing a change") and a strong operational rule: "Base changes on own, never copy applied values into a change." It does not name the sibling tools to use instead or state exclusions, which keeps it 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.