Maître d'MCP

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

No annotations provided, so description carries full burden. Discloses multi-platform search scope (Resy/OpenTable), sorting behavior ('sorted by proximity to this time'), and empty-result handling ('message if none found'). Missing: explicit readOnly/safety declaration, rate limits, or auth requirements.

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?

Uses efficient docstring format with clear Args/Returns sections. Front-loaded with core action. No redundant text—every sentence adds value (platform scope, date examples, sorting logic). Well-structured for parsing.

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?

Comprehensive given constraints. Covers 4 parameters with 0% schema coverage, explains output schema content ('time slots with platform info'), and behavioral nuances. Output schema exists so return values don't need full detailing. Could mention credential requirements for the platforms.

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 has 0% description coverage. Description fully compensates by documenting all 4 parameters with rich semantics: date includes flexible parsing examples ('Saturday', 'tomorrow'), party_size clarifies 'diners', preferred_time notes sorting side-effect. Comprehensive parameter guidance.

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?

Clear specific verb 'Check' + resource 'reservation availability'. Explicitly mentions searching 'both Resy and OpenTable', which distinguishes it from sibling 'make_reservation' (which books) and 'search_restaurants' (which finds restaurants, not slots).

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?

Provides implicit context by describing multi-platform search behavior, but lacks explicit guidance on when to use this vs 'make_reservation' (e.g., 'use this to find available slots before booking'). No mention of prerequisites like stored credentials.

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