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

With readOnlyHint=true already signaling a safe read, the description adds the auth scope requirement, which annotations do not convey. Beyond that it says only 'basic details' without indicating what fields or structure come back, so the disclosure of behavior is thin.

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 purpose and followed by the permission requirement. There is no filler or repetition.

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 zero-argument, read-only lookup, an agent has enough to invoke it correctly. The one gap is that 'basic details' never gets defined and there is no output schema, so the expected response shape remains unknown.

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?

The tool takes zero parameters, so there is nothing for the description to compensate for; schema coverage is 100% and the empty object is self-explanatory. Baseline 4 applies.

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?

Specific verb (get) + resource (property/hotel details) with a scope qualifier -- 'the property the API key is bound to' -- that makes clear this is a single-object lookup, not a listing. It implicitly distinguishes it from siblings like list_rooms or get_daily_rates, though it never names them.

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 states the required auth scope ('read:hotel'), which is a real prerequisite for a caller. However, it gives no guidance on when to reach for this versus other endpoints (e.g. when you need room-level vs property-level data), so usage is only implied.

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