brilliant-directories-mcp

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Delete a menu item' implies a destructive operation, but it doesn't specify whether deletion is permanent, reversible, requires specific permissions, or has side effects (e.g., affecting related data). The description fails to provide any behavioral context beyond the basic action implied by the name.

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 extremely concise at just three words. It's front-loaded with the core action and resource, with no unnecessary elaboration. While this brevity contributes to under-specification in other dimensions, as a standalone statement it wastes no words and follows a clear subject-verb-object structure.

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 destructive nature (implied by 'delete'), absence of annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It doesn't address safety concerns, parameter meaning, expected outcomes, or error conditions. For a mutation tool with no structured documentation support, this minimal description fails to provide necessary context for safe and effective use.

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?

The input schema has 1 parameter (menu_item_id) with 0% description coverage. The tool description adds no information about this parameter—it doesn't explain what a menu_item_id is, how to obtain it, format requirements, or valid ranges. With schema coverage at 0%, the description fails to compensate, leaving the parameter completely undocumented.

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 'Delete a menu item' restates the tool name 'deleteMenuItem' almost verbatim, making it tautological. While it identifies the resource (menu item) and action (delete), it doesn't distinguish this tool from other delete operations in the sibling list (e.g., deleteCategory, deleteUser). The purpose is recognizable but lacks specificity about what makes menu item deletion unique.

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 no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing menu item ID), what happens after deletion, or relationships to other tools like createMenuItem or updateMenuItem. With many sibling tools available, this lack of context leaves the agent guessing about appropriate usage scenarios.

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