Get Property

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering safety. The description adds value by listing specific fields returned (owner_id, check-in/out rules, capacity, address), which goes beyond annotations and helps the agent understand the response content. No contradictions found.

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 description is one concise sentence, front-loaded with the main action and resource, followed by a parenthetical list of detail fields. Every part is informative, and there is no redundant or filler content.

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, single-parameter read-only tool, the description provides sufficient context: it states what it does, what fields are included, and is backed by comprehensive annotations. No output schema exists, but the description gives enough detail for the agent to select and invoke the tool correctly.

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 100% for the single parameter 'id', with a clear description in the schema. The tool description does not add additional parameter information beyond 'by id', which matches the schema. Therefore, the baseline score of 3 is appropriate.

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 clearly states the tool fetches a single property by id, with a specific verb ('Fetch') and resource ('property'). It distinguishes from sibling tools like ownerrez_list_properties and ownerrez_get_booking by explicitly naming the target resource and indicating single-item retrieval with full detail.

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 description implies usage when you need a specific property's full details by its id, but it does not explicitly mention when not to use it or suggest alternatives. There is no direct comparison to sibling tools such as ownerrez_list_properties, so usage context is implied rather than explicit.

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