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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the trailing 'Read-only.' mostly restates structured data. The enumeration of returned content (prices by season, beach distance, owner confirmation date, Telegram link) adds useful substance, but there is no disclosure of permissions, rate limits, or behavior on a missing id.

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 front-loaded sentence naming the resource first, then the payload highlights, then the access mode. Nothing is padded, and the phrase 'by its id from search_properties' is doing genuine routing work.

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 one required parameter and an output schema, the description need not explain return shape, yet it still previews the notable fields. It is complete enough to invoke correctly; the only gap is no note on what happens when the id is unknown or malformed.

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% with a single documented 'id' field and an example value, so the schema carries the parameter burden. The description only adds that the id originates from search_properties, which is marginal but real context beyond the schema; baseline 3 fits.

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 ('Full details of one place by its id') and scopes it to a single record, which cleanly separates it from search_properties (many) and compare_properties (multiple). An agent knows exactly what it retrieves without opening the schema.

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?

'by its id from search_properties' tells the agent the prerequisite step and where the id comes from, which is real usage guidance. It stops short of explicitly excluding compare_properties or describing error behavior for an unknown id, so it is clear context rather than a full when/when-not rule set.

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