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 no information beyond the basic action. It doesn't mention whether this is a read-only operation, if it requires authentication, potential error conditions (e.g., invalid ID), or what the return format might be (e.g., JSON object). This is inadequate for a tool with no annotation support.

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, 'Get a single tag', which is front-loaded and wastes no words. Every part of the sentence earns its place by specifying the action and resource, making it efficient despite its brevity.

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 low complexity (one parameter) but no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't provide enough context for the agent to understand how to use the tool effectively, such as parameter details, behavioral traits, or expected outputs, making it insufficient for reliable operation.

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 schema description coverage is 0%, meaning the parameter 'id' is undocumented in the schema. The description adds no meaning beyond the schema—it doesn't explain what 'id' represents (e.g., a numeric tag identifier), its format, or constraints. With one required parameter and no schema documentation, the description fails to compensate for the coverage gap.

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' clearly states the action (get) and resource (tag), but it's vague about what 'get' entails (e.g., retrieve details, fetch metadata) and doesn't differentiate from sibling tools like 'listTags' or 'getTagGroup', which handle multiple tags or tag groups. It avoids tautology by not restating the name/title, but lacks specificity.

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 such as 'listTags' for multiple tags or 'getTagGroup' for tag groups. The description implies usage for retrieving a single tag but doesn't mention prerequisites (e.g., needing a tag ID) or exclusions, leaving the agent to infer context from the schema alone.

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