brilliant-directories-mcp

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states 'Create a category group' without mentioning any behavioral traits such as required permissions, whether this is a mutating operation, what happens on success/failure, or any side effects. For a creation tool with zero annotation coverage, this is completely inadequate.

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 maximally concise with just three words: 'Create a category group.' It is front-loaded with the core action and resource, though this brevity comes at the cost of meaningful content. Every word serves a basic purpose, with no wasted text.

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 (a creation operation with 4 parameters, 3 required), complete lack of annotations, 0% schema description coverage, and no output schema, the description is severely incomplete. It fails to address what the tool does beyond the name, how to use it, what parameters mean, or what to expect in return, making it inadequate for effective tool selection and invocation.

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 schema description coverage is 0%, meaning none of the 4 parameters (group_name, group_filename, database, group_desc) have any documentation in the schema. The description provides zero information about these parameters—not even mentioning their existence, let alone explaining their purpose, format requirements, or relationships. This 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 'Create a category group' is a tautology that merely restates the tool name without adding meaningful context. It specifies the verb ('create') and resource ('category group'), but provides no information about what a 'category group' is, its purpose in the system, or how it differs from similar resources like 'category' or 'tag group' among the many sibling tools.

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 absolutely no guidance on when to use this tool versus alternatives. With sibling tools like 'createCategory', 'createTagGroup', and 'updateCategoryGroup' available, there is no indication of the specific use case for creating a category group, prerequisites, or how it relates to other creation or management operations in the system.

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