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. It mentions that the system 'finds members matching category, location, and service area' and 'sends notification emails', which gives some context about the matching criteria and side effects. However, it doesn't disclose important behavioral traits like whether this is a read-only or mutation operation, what permissions are required, whether it's idempotent, or what happens on failure. The description is insufficient for a mutation tool with zero annotation coverage.

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 appropriately concise with two sentences that efficiently convey the core functionality. The first sentence states the purpose, and the second explains the process. There's no wasted language, though it could be slightly more structured with clearer separation of concerns.

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 this is a mutation tool (implied by 'Auto-match' and email sending) with no annotations, 0% schema coverage, and no output schema, the description is incomplete. It doesn't explain what happens after matching, what the return value is, error conditions, or important constraints. For a tool that appears to modify data and send notifications, this level of documentation 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 0%, so the description must compensate for the undocumented parameter. The description mentions 'lead_id' implicitly through 'Auto-match lead to members', but doesn't explain what a lead_id is, where to find it, or its format. It adds minimal meaning beyond the bare schema, failing to adequately document the single required parameter.

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 clearly states the tool's purpose: 'Auto-match lead to members' specifies the verb (auto-match) and resource (lead to members). It distinguishes from siblings like 'createLeadMatch' or 'listLeadMatches' by focusing on automatic matching rather than manual creation or listing. However, it doesn't explicitly contrast with all siblings, so it's not a perfect 5.

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. It mentions the tool 'triggers automatic matching' but doesn't specify prerequisites, conditions, or when to choose this over manual matching tools like 'createLeadMatch'. There's no mention of when-not-to-use scenarios or explicit alternatives.

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