brilliant-directories-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure but provides none. 'Delete a category' implies a destructive mutation but doesn't specify whether this is reversible, what permissions are required, what happens to associated data, or any error conditions. For a destructive operation with zero annotation coverage, this is dangerously inadequate and could lead to unintended data loss.

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 at three words. There's no wasted language or unnecessary elaboration. While this conciseness comes at the expense of completeness, the description itself is efficiently structured with zero redundant elements.

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?

For a destructive deletion tool with no annotations, 0% schema description coverage, and no output schema, the description is completely inadequate. It doesn't explain what 'category' means in this context, what the deletion entails, what the parameter requires, or what happens after deletion. This leaves the agent with insufficient information to use the tool safely or effectively.

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 'category_id' has no documentation in the schema. The description provides no information about this parameter - not what it represents, how to obtain valid values, format requirements, or constraints. For a tool with undocumented parameters, the description fails completely to compensate.

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 category' restates the tool name 'deleteCategory' almost verbatim, making it tautological. It specifies the verb 'delete' and resource 'category', but doesn't distinguish from sibling tools like 'deleteCategoryGroup' or 'deleteTag' beyond the resource name. This is minimal differentiation that doesn't provide meaningful context about what makes this deletion operation 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 absolutely no guidance about when to use this tool versus alternatives. There are multiple sibling deletion tools (deleteCategoryGroup, deleteTag, deletePost, etc.) but no indication of when this specific category deletion is appropriate versus other deletion operations. No prerequisites, constraints, or alternative tools are mentioned.

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