federation-mcp-server

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it filters results by availability and guest count, and includes live pricing with public and federation rates. However, it lacks details on permissions, rate limits, pagination, or error handling, which are important for a search tool.

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 appropriately sized and front-loaded, with two sentences that efficiently convey the tool's purpose, filtering criteria, and return details. Every sentence adds essential information without waste.

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?

Given the tool's moderate complexity (5 parameters, no output schema, no annotations), the description is adequate but has gaps. It covers the core functionality and return values well, but lacks information on behavioral aspects like pagination, error cases, or authentication needs, which would enhance completeness.

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 100%, so the schema already documents all parameters thoroughly. The description adds marginal value by implying that 'region' and 'country' are for location filtering, and 'guests', 'checkIn', and 'checkOut' are used for availability and accommodation checks, but doesn't provide additional syntax or format details beyond the schema.

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's purpose with specific verbs ('search vacation rental properties') and resources ('properties'), and distinguishes it from siblings by specifying it returns available properties with pricing, unlike check_availability (likely just availability), create_booking (booking creation), or get_canonical_quote (quote generation).

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 provides clear context for when to use this tool ('search vacation rental properties by location and travel dates'), implying it's for finding available properties with pricing. However, it doesn't explicitly state when not to use it or name alternatives (e.g., use check_availability for availability-only checks), though the sibling tools suggest distinct purposes.

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