brilliant-directories-mcp

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

No annotations are provided, so the description carries the full burden. 'Get' suggests a read-only operation, but it doesn't disclose behavioral traits such as authentication needs, rate limits, error handling, or what the return includes (e.g., fields, format). This is a significant gap for a tool with no 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 a single, efficient sentence with no wasted words, making it front-loaded and easy to parse. It's appropriately sized for a simple tool, though it could benefit from more detail without sacrificing conciseness.

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 complexity (a read operation with one parameter), no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It lacks details on behavior, return values, and usage context, making it inadequate for an agent to fully understand how to invoke the tool correctly.

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 description doesn't add meaning beyond the input schema, which has 0% description coverage and only one parameter ('smart_list_id'). However, with 0 parameters effectively (since the schema lacks descriptions), the baseline is 4 as the description doesn't need to compensate for missing param info, but it also doesn't enhance understanding of the parameter's purpose or format.

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 smart list' clearly states the verb ('Get') and resource ('smart list'), but it's vague about what 'Get' entails (e.g., retrieve details, fetch metadata) and doesn't distinguish from siblings like 'listSmartLists' or 'getSmartList' (if it exists elsewhere). It's minimally adequate 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 like 'listSmartLists' for multiple smart lists or other 'get' tools for different resources. The description implies usage for a single smart list but doesn't specify prerequisites, exclusions, or context, leaving the agent to infer based on naming alone.

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