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. The description adds nothing beyond that — no error behavior for unknown IDs, no note about required brokerage scoping, no rate or volume limits.

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?

One short, front-loaded sentence with no waste, but it is under-specified rather than genuinely concise — the brevity comes at the cost of routing information the agent needs.

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 read tool with no output schema and 11 siblings, the description should clarify what fields come back and how it relates to search_properties. The nested id+brokerage requirement is only in the schema, and no guidance on the single-vs-bulk tradeoff is given.

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% and the single 'listings' array parameter is well documented in the schema, so baseline 3 applies. The description's 'single or several' phrasing mildly reinforces the array semantics but adds no new detail about the required id/brokerage pair.

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 verb ('Get details') and resource ('listing'), and adds that it supports one or many listings. However, it largely restates the title and name, and does not distinguish the tool from search_properties or save_listings, which operate on the same resource.

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?

There is no indication of when to use this tool versus search_properties (discovery) or save_listings (persistence). An agent must infer that this is a fetch-by-ID tool for listings it already knows about.

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