brilliant-directories-mcp

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states 'Create a menu item', failing to mention that this is a write operation (implied by 'Create'), potential side effects (e.g., database insertion), authentication requirements, error conditions, or response format. This leaves critical behavioral aspects undocumented, making it inadequate for safe invocation.

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 with just three words, which is front-loaded and wastes no space. However, this brevity comes at the cost of under-specification—it lacks necessary details for effective use. While structurally minimal, it doesn't achieve helpful conciseness due to missing critical information.

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 complexity (9 parameters, 5 required, mutation operation), lack of annotations, and absence of an output schema, the description is severely incomplete. It doesn't explain what a menu item is, how to use it, what parameters mean, or what to expect upon creation. This fails to provide adequate context for the agent to operate the tool correctly.

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 description coverage is low at 44%, with 5 of 9 parameters lacking descriptions in the schema. The tool description adds no information about parameters, not even hinting at their purposes (e.g., hierarchical structure via 'master_id', activation states via 'menu_active'). Given the low coverage, the description fails to compensate, leaving most parameters semantically unclear.

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 'Create a menu item' is a tautology that merely restates the tool name. It lacks specificity about what a 'menu item' entails in this context, such as navigation elements with display text, links, and hierarchical structure. While it indicates a creation action, it doesn't differentiate from sibling tools like 'createMenu' or 'createCategory', which also create related entities.

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 or parent item), exclusions, or comparisons to sibling tools like 'createMenu' (for creating menus) or 'updateMenuItem' (for modifying existing items). This absence leaves the agent without context for appropriate tool selection.

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