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 mention whether this is a read-only operation, if it requires authentication, its rate limits, or what the output looks like (e.g., pagination, format). This leaves critical behavioral traits unspecified for a search function.

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 just two words, which is efficient but under-specified. It is front-loaded but lacks necessary detail, making it more of an under-description issue than a structural flaw. No wasted sentences, but it fails to provide adequate information.

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 complexity (search functionality with parameters), lack of annotations, and no output schema, the description is incomplete. It does not explain what the tool returns, how results are structured, or behavioral aspects like permissions or limitations, leaving significant 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?

Schema description coverage is 50% (one parameter has a detailed enum description, the other has none). The description adds no parameter information beyond what the schema provides, failing to compensate for the undocumented 'user_id' parameter. However, the schema's enum description for 'review_status' is comprehensive, justifying a baseline score of 3 as it does some heavy lifting.

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 'Search reviews' is a tautology that merely restates the tool name without specifying what 'search' entails (e.g., filtering by criteria, returning results). It lacks a clear verb-resource combination and does not differentiate from sibling tools like 'listReviews' or 'getReview', leaving the agent uncertain about its specific function.

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 'listReviews' or 'getReview'. The description offers no context, prerequisites, or exclusions, making it impossible for an agent to determine appropriate usage scenarios without external knowledge.

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