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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds genuine value with the visibility/freshness filtering rule, which is behavior an agent cannot get from annotations or schema, plus a data-semantics warning about distinguishing field observation dates from lastObservedAt.

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?

Three short sentences with the core action front-loaded and no filler. The trailing sentence on observation dates is tersely phrased and slightly cryptic out of context, but it is carrying real data semantics rather than padding.

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 no output schema, the description would ideally sketch what a returned property looks like or how it signals a suppressed record; instead the agent must infer that from the unavailability sentence. For a simple two-parameter read with full annotation coverage, it is adequate but leaves return-value expectations unstated.

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 coverage is only 50%: catalogId carries a description about public catalog links and GEO-independent MCP access, while id is documented only by its UUID pattern. The description says 'by its ID' but never mentions catalogId or explains how the two identifiers relate, so the one schema-documented parameter is the only one with real semantics.

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 by its ID'), which is unambiguous on its own. It does not differentiate itself from the sibling get_findestate_property, so an agent must infer the distinction from name alone.

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 second sentence gives a meaningful when-not condition by enumerating record states (hidden, incomplete, withdrawn, stale, unproven-price) that will not be returned, which tells the agent when this lookup will come back empty. However, no alternative tools are named for the cases where this one fails, and there is no explicit 'use this when' framing.

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