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 tag' implies a destructive mutation, but it doesn't specify whether deletion is permanent, requires specific permissions, has side effects (e.g., cascading deletions), or returns confirmation. This is inadequate for a destructive operation with zero annotation coverage.

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, front-loading the core action. There's no wasted language, though this brevity comes at the cost of completeness. Every word earns its place, even if insufficient.

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, lack of annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It doesn't explain the parameter, behavioral implications, or expected outcomes, leaving critical gaps for safe and correct usage.

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 0%, meaning the single parameter 'id' is undocumented in the schema. The description provides no information about this parameter—not what it represents (e.g., tag ID), its format, or where to obtain it. The description fails to compensate for the complete lack of schema documentation.

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 tag' restates the tool name 'deleteTag' almost verbatim, making it tautological. While it indicates the action (delete) and resource (tag), it provides no additional specificity about what deletion entails or how it differs from other delete operations in the sibling list.

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 offers no guidance on when to use this tool versus alternatives. With sibling tools like 'deleteTagGroup', 'deleteTagRelationship', and 'deleteTagType', there's no indication of how this tool differs or when it's appropriate. No prerequisites, constraints, or usage context are mentioned.

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