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 but fails to disclose behavioral traits. It doesn't mention if deletion is permanent, requires specific permissions, has side effects, or provides confirmation, leaving the agent uninformed about critical operational aspects.

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 with a single sentence, 'Delete a lead match', which is front-loaded and wastes no words. However, this brevity contributes to under-specification rather than effective communication.

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 destructive nature (implied by 'delete'), lack of annotations, no output schema, and 0% schema coverage, the description is severely incomplete. It fails to address safety, outcomes, or error handling, making it inadequate for informed tool invocation.

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%, so the description must compensate but adds no parameter information. It doesn't explain what 'match_id' represents, its format, or constraints, leaving the single required parameter undocumented beyond its type in the schema.

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 'Delete a lead match' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'delete' and resource 'lead match', but doesn't clarify what a 'lead match' is or how it differs from other deletion tools like 'deleteLead' or 'deleteTag', missing sibling differentiation.

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 such as 'deleteLead' or 'updateLeadMatch'. The description lacks context about prerequisites, conditions for deletion, or any exclusions, offering no usage instructions.

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