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. It states 'Delete', implying a destructive mutation, but fails to mention critical details like required permissions, whether the deletion is permanent or reversible, side effects, or error conditions. This leaves significant gaps for safe tool invocation.

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 tag relationship', which is front-loaded and wastes no words. While under-specified, it is structurally efficient and earns its place by stating the core action without redundancy.

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 (implied by 'Delete'), no annotations, a single undocumented parameter, and no output schema, the description is severely incomplete. It does not provide enough information for an AI agent to understand the tool's behavior, inputs, or outcomes safely and 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?

The input schema has 1 parameter ('id') with 0% description coverage, and the tool description adds no semantic information about this parameter. It does not explain what 'id' refers to (e.g., a relationship ID, tag ID, or other identifier), its format, or constraints, failing to compensate for the schema's lack of 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 relationship' is a tautology that merely restates the tool name without adding meaningful context. While it identifies the verb ('Delete') and resource ('tag relationship'), it lacks specificity about what a 'tag relationship' entails or how it differs from other tag-related operations like 'deleteTag' or 'deleteTagGroup' among the 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 no guidance on when to use this tool versus alternatives. With sibling tools like 'deleteTag', 'deleteTagGroup', and 'updateTagRelationship', there is no indication of prerequisites, exclusions, or contextual cues to help an AI agent choose appropriately, making it misleading in a crowded namespace.

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