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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds genuinely non-obvious behavior: content is returned in English with language prefixes for thirteen other languages, which directly affects how the agent should present or post-process the response. It does not mention caching or freshness of the static data, which would have pushed it higher.

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?

It is a single long run-on sentence built as a comma-separated enumeration of return fields, with the one actionable detail (English plus thirteen language prefixes) buried at the end. Much of the enumeration duplicates the output schema rather than earning its place in the description.

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?

Because an output schema exists, the description need not enumerate return contents — yet that enumeration is nearly all it does. What it omits is the part only prose can supply: the absence of any input requirement, and the relationship to the three sibling tools. Adequate but with clear gaps for a no-param retrieval tool.

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 disambiguate and the baseline of 4 applies. The schema's 100% coverage is trivially satisfied.

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 makes clear this returns static descriptive information about the property — identity, address, coordinates, amenities, practical stay facts, directions, booking URLs — so an agent knows exactly what resource it retrieves. It is a noun-phrase content list rather than an explicit verb+resource statement, and it never names the siblings (check_room_availability, get_availability_calendar, list_public_events) to draw the line, but the domain separation is self-evident.

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 guidance on when to call this versus the availability/calendar/events siblings, and no statement that it takes no inputs and needs no prior call. The agent must infer that this is the 'fetch the hotel's static profile' tool from the content list alone.

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