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 for behavioral disclosure. 'Create a smart list' implies a write/mutation operation but offers no details on permissions required, side effects, error handling, or what constitutes a successful creation. It doesn't describe the return value or any system constraints, leaving critical behavioral aspects unspecified.

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 at three words, with no wasted language. However, this brevity comes at the cost of under-specification—while structurally minimal, it fails to provide necessary context that would require more content.

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 5 parameters, no annotations, no output schema, and 60% schema coverage, the description is severely incomplete. It doesn't address what a smart list is, how it differs from other entities, what happens after creation, or any operational constraints. For a creation tool with multiple parameters and no structured support, this minimal description is inadequate.

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 60%, with 3 of 5 parameters having descriptions in the schema. The tool description adds no parameter information beyond what's in the schema—it doesn't explain the purpose of smart_list_type enum values, how query_params are formatted, or what schedule frequencies are valid. With incomplete schema coverage and no compensatory details in the description, parameter understanding remains inadequate.

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 smart list' is a tautology that restates the tool name without adding meaningful context. It specifies the verb 'create' but doesn't explain what a 'smart list' is or what distinguishes it from other creation tools like createCategory or createForm. The purpose remains vague beyond the basic action implied by the 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?

The description provides no guidance on when to use this tool versus alternatives. There are multiple sibling creation tools (e.g., createCategory, createForm, createLead), but the description doesn't differentiate this tool's use case, mention prerequisites, or specify when it's appropriate versus other list-related tools like listSmartLists or updateSmartList.

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