brilliant-directories-mcp

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a safe operation, what permissions might be required, whether changes are reversible, what happens on success/failure, or any side effects. 'Update' implies mutation but gives no behavioral context about what that entails.

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 just four words, with no wasted language. While this conciseness comes at the cost of completeness, the structure is front-loaded with the core action and resource. Every word serves a purpose, even if that purpose is insufficient.

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 mutation tool with 2 parameters (0% documented), no annotations, no output schema, and no sibling differentiation, this description is completely inadequate. It doesn't explain what a tag relationship is, what gets updated, what the parameters do, what behavior to expect, or when to use it. The agent lacks essential context to use this tool 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?

With 0% schema description coverage for both parameters (id and object_id), the description provides zero information about what these parameters mean, their expected formats, or how they relate to updating a tag relationship. The description doesn't mention parameters at all, leaving the agent to guess based on parameter names alone.

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 'Update a tag relationship' is essentially a tautology that restates the tool name 'updateTagRelationship' without adding meaningful specificity. It doesn't explain what a 'tag relationship' is, what aspects can be updated, or how this differs from sibling tools like 'createTagRelationship' or 'deleteTagRelationship'. While the verb 'update' is clear, the resource 'tag relationship' lacks definition.

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. There's no mention of prerequisites (e.g., needing an existing tag relationship), when this is appropriate versus creating or deleting tag relationships, or any contextual constraints. The agent must infer usage entirely from the tool name and schema.

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