Maître d'MCP

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

No annotations provided, so description carries full disclosure burden. It valuablely specifies the dual-platform scope (Resy/OpenTable) and return structure. However, it omits safety characteristics (read-only vs destructive), rate limits, or the definition of 'upcoming' time window.

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 tightly constructed sentences with purpose front-loaded and return values secondary. No redundant words. Appropriate length for a parameter-less retrieval tool.

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?

Adequate for a simple retrieval tool with existing output schema (per context signals). The description covers data source systems and return format. Minor gap: lacks explicit temporal scope definition for 'upcoming' and read-only safety assurance given the presence of destructive siblings.

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?

Zero parameters present, establishing baseline of 4 per rubric. Description correctly implies no filtering is available (returns 'all'), which matches the empty schema. No parameter explanation required or provided.

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 verb (Show) and resource (reservations) with specific scope (upcoming, across Resy/OpenTable). Distinguishes from visit_history (past) and cancel/make siblings by specifying read-only retrieval, though 'Show' is slightly less precise than 'List'.

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?

No explicit guidance on when to use versus alternatives like visit_history or my_wishlist. No mention of prerequisites (e.g., requiring stored credentials from the store_resy_credentials or store_opentable_credentials siblings).

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