brilliant-directories-mcp

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

No annotations are provided, so the description carries full burden. It states 'Get' but doesn't clarify if this is a read-only operation, requires authentication, has rate limits, or what the output includes (e.g., fields, error handling). The description lacks behavioral details beyond the basic action.

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, front-loaded sentence with zero waste: 'Get a single tag group'. It's appropriately sized for a simple tool, though brevity limits informativeness.

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 (1 parameter, no nested objects) but no annotations or output schema, the description is incomplete. It doesn't cover parameter meaning, behavioral traits, or return values, leaving gaps for an AI agent to infer usage.

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 0%, with one parameter 'id' (type integer) undocumented in the schema. The description adds no meaning—it doesn't explain what 'id' refers to (e.g., tag group ID), its format, or where to obtain it. This fails to compensate for the low 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 'Get a single tag group' clearly states the verb ('Get') and resource ('tag group'), but it's vague about what 'Get' entails—retrieving details, metadata, or something else. It distinguishes from siblings like 'listTagGroups' (plural vs. single) but not from other 'get' tools like 'getTag' or 'getTagType' beyond the resource name.

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 doesn't mention prerequisites (e.g., needing an ID), compare to 'listTagGroups' for multiple groups, or specify use cases like editing or viewing details. The description alone offers no usage context.

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