brilliant-directories-mcp

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers none. 'Update' implies a mutation operation, but the description doesn't mention permission requirements, whether changes are reversible, what happens to existing data not specified in parameters, rate limits, or any side effects. This leaves the agent completely in the dark about behavioral characteristics.

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 three words. While this represents severe under-specification, from a pure conciseness perspective, it contains zero wasted words and is front-loaded with the essential action. Every word technically serves a purpose, even if that purpose is insufficient.

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 5 parameters, 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what a smart list is, what can be updated, what the parameters mean, what permissions are required, what the tool returns, or how it differs from related tools. This leaves critical gaps for agent understanding.

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?

With 5 parameters and 0% schema description coverage, the description provides no information about any parameters. It doesn't explain what 'smart_list_id' identifies, what 'smart_list_query_params' contains, what format 'schedule' expects, or what any of the fields actually mean. The description fails completely to compensate for the lack of schema documentation.

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 'Update a smart list' is a tautology that restates the tool name without adding meaningful context. It specifies the verb ('update') and resource ('smart list'), but doesn't explain what a smart list is or what aspects can be updated, making it only slightly better than a pure restatement of 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. With sibling tools like 'createSmartList', 'deleteSmartList', 'getSmartList', and 'listSmartLists', there's no indication of when update is appropriate versus create or delete, nor any mention of prerequisites or constraints for using this tool.

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