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. States it returns a 'Formatted list,' indicating read-only behavior, but lacks safety disclosures (e.g., 'does not modify data'), rate limits, or caching behavior. Adequate but minimal behavioral context.

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?

Front-loaded with action. Two sentences total. The 'Returns:' section is slightly redundant given output schema exists, but overall efficient and well-structured.

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?

Appropriate for complexity: 0 params, output schema present. Description provides essential domain context (dining companions, dietary restrictions) not present in structural fields. Sufficient for agent selection.

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 per empty schema. Baseline score applies; description correctly implies no filtering arguments by stating 'all saved' companions.

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?

Excellent specificity: 'List' (verb) + 'saved dining companions' (resource) + 'dietary restrictions and notes' (scope/data). Clearly distinguishes from generic 'manage_person' sibling by emphasizing bulk retrieval of preferences.

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 when-to-use guidance or contrast with siblings. Missing direction such as 'use manage_person to edit individual companions' or when filtering is needed vs listing all.

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