Property info

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly indicates a read operation returning profile and room catalog, but it does not mention potential errors, response format, or any access requirements. For a simple get tool this is adequate, but it adds minimal behavioral context beyond the name.

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?

The description is a single, information-dense sentence that front-loads the main purpose and parenthetically lists the catalog items. Every word adds value and there is no redundancy or fluff.

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 simple one-parameter read tool with no output schema, the description is sufficient: it tells the agent exactly what data will be returned (profile and room catalog) and the scope (one property). It could add notes about error behavior or return shape, but those are not critical for selection and invocation.

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 schema covers the single parameter fully with a description including an example and a fallback instruction. The tool description adds no additional parameter semantics, but the schema already provides sufficient detail, so the baseline of 3 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?

The description clearly states the tool returns a hotel profile and full room catalog (room types, capacities, amenities) for one property. This distinguishes it from siblings like list_properties (which lists properties) and get_rates/get_availability (which focus on pricing and availability). The scope is specific: 'for one property'.

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 implies this tool is for fetching comprehensive property details and room catalog for a single property, but it does not explicitly state when to prefer it over siblings. It lacks explicit 'when to use' or 'when not to use' guidance. The schema mentions calling list_properties if the property code is unknown, but that is not in the main description.

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