Maître d'MCP

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

With no annotations provided, the description carries full disclosure burden and excels: it explains encryption, local-only storage, that data is only sent to Resy servers, and crucially that 'The password is NOT persisted after authentication.' It also clarifies immediate verification behavior ('error if login failed').

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?

Information-dense and well-structured with clear paragraph breaks and bold headers. Every sentence earns its place, particularly the security guarantees which are critical for a credential tool. Slightly verbose formatting with Args/Returns sections, but necessary given the lack of schema documentation.

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?

Excellent completeness for a sensitive security operation. Covers purpose, security model, storage lifecycle (password not persisted), parameter semantics, and return behavior. Since output schema exists, the brief return summary is appropriate and adds context about verification.

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?

Given 0% schema description coverage, the description comprehensively compensates by documenting both parameters in the Args section and explaining their relationship to environment variables ('or set RESY_EMAIL env var'), which the schema cannot express.

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 uses a specific verb 'Save' with the exact resource 'Resy account credentials' and clarifies the purpose is 'for automated booking.' It clearly distinguishes from the sibling store_opentable_credentials by specifying the Resy platform.

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 explicit guidance on when to call with no arguments ('If env vars are set, call this tool with no arguments') versus providing credentials inline. However, it does not explicitly mention when to prefer this over store_opentable_credentials, though the distinction is implied by the platform names.

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