brilliant-directories-mcp

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action 'Get', implying a read operation, but fails to describe any behavioral aspects such as permissions needed, error handling, rate limits, or what 'Get' entails (e.g., retrieval by ID). This leaves critical gaps for safe and effective use.

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 a single, straightforward sentence with no wasted words, making it highly concise. However, this conciseness comes at the cost of under-specification, as it lacks necessary details for effective tool use.

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 read operation with 1 parameter), lack of annotations, 0% schema coverage, and no output schema, the description is severely incomplete. It does not provide enough context for the agent to understand what the tool does, how to use it, or what to expect, making it inadequate for reliable 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 input schema has 1 parameter with 0% description coverage, and the description adds no semantic information about the 'id' parameter. It does not explain what the ID represents, its format, or where to obtain it, 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 'Get a single tag relationship' restates the tool name 'getTagRelationship' almost verbatim, making it tautological. It specifies the verb 'Get' and resource 'tag relationship', but lacks any distinguishing details about what a tag relationship is or its scope compared to siblings like 'listTagRelationships' or 'getTag'.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention prerequisites, context, or differentiate from sibling tools like 'listTagRelationships' (for multiple items) or 'getTag' (for related resources), leaving the agent with no usage direction.

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