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 fails completely. 'Create a tag' implies a write/mutation operation but provides no information about permissions required, whether the operation is idempotent, what happens on duplicate tag names, what the response contains, or any error conditions. 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 maximally concise with just two words. While severely under-specified, it contains no wasted words and is front-loaded with the essential action. This is the one dimension where the description performs well, though this conciseness comes at the expense of completeness.

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 3 required parameters, 33% schema description coverage, no annotations, and no output schema, the description is completely inadequate. It provides no information about the operation's behavior, parameter meanings, success/failure conditions, or relationship to sibling tools. The description fails to provide the minimal context needed for an agent 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?

Schema description coverage is only 33% (only 'added_by' has a description), and the description 'Create a tag' provides zero parameter information. The three required parameters (tag_name, group_tag_id, added_by) receive no explanation in the description about their purpose, format constraints, or relationships. The description fails to compensate for the low schema coverage.

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 'Create a tag' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'create' and resource 'tag', but doesn't distinguish this from sibling tools like createTagGroup, createTagType, or createTagRelationship. The description lacks specificity about what kind of tag is being created or its purpose within the system.

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 are multiple related tag creation tools (createTagGroup, createTagType, createTagRelationship) with no indication of how they differ or when each should be used. No prerequisites, constraints, or contextual usage information is provided.

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