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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds genuinely new behavioral context the annotations cannot convey: the amount convention ('integer cents in the property's currency') and the full breadth of returned data. It stops short of stating behavior for missing/invalid ids or pagination, but that is a minor gap against a fully declared safe-read profile.

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 purpose is front-loaded in the opening clause, and the long field enumeration is justified because there is no output schema to describe the return payload. The comma-separated list is dense and unstructured rather than categorized, but every item earns its place as return-value documentation.

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 correctly assumes responsibility for describing the return payload, and it does so thoroughly while also fixing the currency/unit convention — a detail easy to get wrong. For a low-complexity single-parameter read tool guarded by complete annotations, the only meaningful omissions are error/not-found behavior and how it differs from sibling lookups.

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 description coverage is 100% for the single propertyId parameter, so the schema already carries the parameter documentation and the baseline of 3 applies. The description only restates that the input is 'a property id' and adds no format, prefix, or validity detail beyond the schema's 'A RentalCal property id.'

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 states a specific verb+resource ('The full listing for a property id') and enumerates exactly what the listing contains, so an agent knows this returns the complete property record rather than a summary. It does not explicitly name or contrast with siblings like find_property or get_quote, though the 'full listing' framing implicitly separates it from search-style tools.

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: the phrase 'for a property id' signals the precondition that an id must already be known, which naturally routes an agent here after find_property. There is no explicit when-to-use or when-not-to-use statement, and no mention of the alternatives (find_property, get_quote) that an agent might otherwise choose.

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