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. 'Create a category' implies a write/mutation operation but reveals nothing about permissions, side effects, error conditions, or response format. It doesn't indicate whether creation is idempotent, what happens on duplicate names, or if it triggers other system changes. This leaves critical behavioral traits completely undocumented.

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, with zero wasted language. It's front-loaded with the core action and resource. While this brevity contributes to under-specification in other dimensions, as pure conciseness it's optimal—every word earns its place by stating the essential function.

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 complexity (a creation/mutation tool with 5 parameters, 3 required), absence of annotations, no output schema, and low schema description coverage, the description is completely inadequate. It doesn't address behavioral risks, parameter meanings, expected outcomes, or differentiation from siblings. For a tool that likely modifies system state, this minimal description leaves too many gaps for reliable agent 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?

Schema description coverage is only 20% (only 'filename' has a description as 'URL-friendly slug'), leaving 4 parameters undocumented. The description adds no parameter information beyond the tool name—it doesn't explain what 'name', 'group_id', 'keywords', or 'icon' represent, their formats, or relationships. While the schema defines types and requirements, the description fails to compensate for the low coverage with any semantic context.

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 category' is a tautology that restates the tool name without adding meaningful context. It specifies the verb ('Create') and resource ('category') but lacks specificity about what a category represents in this system or how it differs from similar resources like 'CategoryGroup' or 'Tag'. This minimal statement fails to distinguish the tool from its many sibling 'create' operations.

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 group_id), exclusions, or comparisons to sibling tools like 'createCategoryGroup' or 'updateCategory'. Without any usage context, an agent must infer everything from the tool name and parameters alone.

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