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

readOnlyHint=true already tells the agent this is a safe read, so the description carries a lighter burden. What it adds is only the REST endpoint mapping (GET /properties/{propertyId}); it says nothing about not-found/error behavior or what the returned property object contains, which is the main remaining ambiguity for a getter.

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?

Two short sentences, front-loaded with the operative verb and resource, then the endpoint mapping. No filler or repetition; every clause earns its place.

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 simple one-parameter read, the definition plus annotations is minimally sufficient to invoke it correctly. However, with no output schema and no mention of the returned property shape or failure modes, the description leaves the agent guessing about the result — a gap it could have closed in a sentence.

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 with 100% schema description coverage ('The property_id (from the matching list tool)'), so the schema already does the work. The description adds no format, validation, or sourcing detail beyond restating that lookup is by id, which matches the baseline 3 for full schema coverage.

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 ('Get one property') and the singular 'one ... by id' implicitly contrasts with the sibling doorloop_list_properties. It stops short of naming the sibling or clarifying scope differences explicitly, but an agent can still tell retrieval-by-id from listing.

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?

Usage is only implied: fetch a single property when you already have its id. There is no explicit statement of when to prefer this over doorloop_list_properties, and no mention of what to do if the id is unknown — though the schema parameter hints at sourcing ids from the matching list tool.

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