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 fails to do so. It does not indicate if this is a read-only operation, requires authentication, has rate limits, or describes the return format. This omission is critical for a tool that likely retrieves sensitive data.

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, 'Get a single lead', 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 complexity of a data retrieval tool with no annotations, 0% schema coverage, and no output schema, the description is completely inadequate. It lacks essential details like authentication needs, error handling, or what 'lead' data includes, making it insufficient for safe and effective use.

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 input schema has 0% description coverage, with one required parameter 'lead_id' of type integer. The description adds no meaning beyond the schema, such as explaining what a 'lead_id' is, its format, or where to find it, failing to compensate for the schema's lack of detail.

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 lead' restates the tool name 'getLead' with minimal elaboration, making it tautological. It specifies the verb 'Get' and resource 'lead', but lacks detail on what 'lead' entails or how it differs from sibling tools like 'listLeads' or 'getLeadMatch', leaving the purpose vague.

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 'listLeads' for multiple leads or 'getLeadMatch' for related data. The description offers no context, prerequisites, or exclusions, leaving the agent without usage direction.

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