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 but offers no behavioral details. It does not disclose that this is a destructive operation, specify permissions required, indicate if deletion is permanent or reversible, mention side effects, or describe error handling. This is inadequate for a mutation tool 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 a single sentence, 'Delete a widget', which is front-loaded and wastes no words. While under-specified, it is structurally efficient with no redundant phrasing.

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, no output schema, and multiple sibling tools, the description is severely incomplete. It fails to address critical aspects like safety, parameters, outcomes, or differentiation, making it inadequate for effective tool 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 0%, so the description must compensate but adds no parameter information. It does not explain what 'widget_id' represents, its format, or where to obtain it. The description fails to provide any semantic context beyond the schema's basic type and requirement, leaving the parameter undocumented.

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 widget' restates the tool name 'deleteWidget' with minimal elaboration, making it tautological. While it clearly indicates a deletion action on a 'widget' resource, it lacks specificity about what a widget is or how this differs from other delete operations like deleteCategory or deleteUser 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 provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing a widget_id), when deletion is appropriate, or what happens post-deletion, leaving the agent with no contextual cues for selection among the many delete and other sibling tools.

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