airbnb-data

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It discloses no side effects, read-only hints, destructive actions, permissions, rate limits, or expected behavior. There is no behavioral information at all.

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 extremely short, but this is under-specification rather than concise clarity. It contains no useful information and is not front-loaded with actionable content.

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 tool with three undocumented parameters, no output schema, and no annotations, the description is wholly inadequate. An agent cannot determine the operation, required inputs, or return value.

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 input schema shows three parameters (start, end, roomId) with no descriptions and 0% schema description coverage. The description adds no meaning to any parameter, so the agent cannot know the expected format, units, or purpose of these arguments.

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 'V1 Airbnb Calendar' merely restates the tool name with a version label and contains no verb or statement of functionality. It does not say whether the tool fetches availability, manages bookings, or performs some other calendar action, nor does it distinguish it from sibling tools.

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 use this tool versus airbnb_details or airbnb_search. No context, conditions, or alternatives are mentioned.

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

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

No annotations are provided, so the description carries the full burden of disclosing behavior. 'V1 Airbnb Details' discloses nothing about side effects, whether the operation is read-only, required permissions, rate limits, or output behavior. This is effectively no behavioral disclosure.

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 short, but that is under-specification rather than effective conciseness. 'V1' adds versioning noise without value, and the phrase 'Airbnb Details' merely echoes the tool name without earning its place.

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?

Despite having only one parameter and no output schema, the description is inadequate: it does not say what details are returned, how roomId should be obtained, or what the response looks like. The tool is not safely callable based on this definition alone.

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%, and the description adds no meaning about the roomId parameter, such as its format, source, or whether it is required. The parameter name alone is the only hint, and the description does not compensate for the missing schema details.

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 is effectively a restatement of the tool name: 'V1 Airbnb Details' names a resource but uses no verb and gives no action such as fetch, retrieve, or list. It does not help distinguish the tool from sibling tools like airbnb_search or airbnb_calendar.

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 about when to use this tool versus airbnb_search or airbnb_calendar, nor any mention of prerequisites or context. An agent is left to guess whether this tool is for looking up a specific listing's detail after a search or for something else.

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

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about whether the search is read-only, what inputs affect behavior, whether it hits an external API, or what the response looks like. The description offers no behavioral information beyond the tool's 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 short, but that brevity is under-specification rather than effective conciseness. It has no front-loaded useful content and provides no structured information that helps an agent act.

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 four undocumented parameters, no annotations, no output schema, and sibling tools that are not differentiated, the description is far too sparse to support correct invocation. An agent cannot determine valid values, required context, or expected results.

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% and the description mentions none of the four parameters (guests, checkin, checkout, location). The agent receives no explanation of formats, constraints, or how these fields combine, so parameter semantics are entirely undocumented.

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 'V1 Airbnb Search' is essentially a restatement of the tool name 'airbnb_search'. It gives no indication of what the search returns, what scope it covers, or how it differs from siblings like airbnb_calendar and airbnb_details.

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 use this tool versus airbnb_calendar or airbnb_details. The description provides no context, exclusions, or alternative routing, leaving the agent to guess which tool fits the user's intent.

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