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 provides none. 'Create a lead' implies a write/mutation operation but doesn't disclose permissions needed, whether this is idempotent, what happens on duplicate entries, error conditions, or any behavioral traits. For a creation tool with 6 required parameters, this is critically insufficient.

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?

While technically concise with only two words, this is under-specification rather than effective conciseness. The description doesn't provide enough information to be useful, so its brevity is a liability. It's front-loaded only in the sense that there's nothing to load beyond the initial phrase.

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 creation tool with 6 required parameters, no annotations, and no output schema, the description is completely inadequate. It doesn't explain what a lead is, what fields are required, what the operation does, what happens on success/failure, or any behavioral context. This leaves the agent with insufficient information to use 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 schema description coverage is only 17% (only 'top_id' has a description as 'Category ID'), and the description provides zero parameter information. With 6 required parameters (lead_name, lead_email, lead_phone, lead_message, lead_location, top_id), the description doesn't explain what any of these mean, their formats, constraints, or relationships. This fails to compensate for the low schema 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 'Create a lead' is a tautology that restates the tool name without adding specificity. It doesn't explain what a lead is in this context or what resources are involved, though it does include the verb 'create' which indicates a write operation. This provides minimal purpose information beyond the name itself.

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 absolutely no guidance on when to use this tool versus alternatives. With sibling tools like 'createCategory', 'createUser', and 'updateLead', there's no indication of when this specific creation tool is appropriate versus other creation tools or when to use updateLead instead. No context, prerequisites, or exclusions are mentioned.

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