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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so safety is covered. The description adds one real behavioral nuance: the data returned is 'published' only, implying drafts/unpublished content are excluded. It says nothing about behavior for an unknown or stale location_id, or about response size/pagination.

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 sentences, front-loaded with the resource and its payload, followed by the sourcing instruction for the required parameter. The enumeration of fields is dense but every item maps to something an agent might need to answer a question, so nothing is wasted.

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 an output schema present, return shape needn't be described, and the field enumeration is enough for an agent to decide relevance. Minor gap: no statement of what happens on a missing/invalid location_id, and conversation_id is left unexplained for a tool that accepts it.

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 0%, so the description has to carry parameter meaning. It does add value by identifying where location_id comes from (list_locations), but gives no format/validity expectations, and the optional conversation_id parameter is completely unaddressed in both schema and description.

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 the resource precisely ('Everything published about one location') and enumerates the concrete contents — address, transit, amenities, photos, memberships, starting prices, booking link, tour booking. This makes it clearly distinct from list_locations (which enumerates locations) without needing the schema opened.

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?

'Use a location_id from list_locations' gives the agent an explicit prerequisite and the correct upstream sibling. However, no exclusions are stated — e.g. it never says to use get_membership_options instead when the user only wants plan details, or get_tour_slots for availability, despite those siblings being adjacent in scope.

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