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 offers none. 'Create a review' implies a write/mutation operation but doesn't disclose permission requirements, side effects, error conditions, rate limits, or what happens upon success. This is particularly problematic for a creation tool with 8 parameters and no output schema.

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 maximally concise at just two words. While this represents severe under-specification rather than ideal conciseness, from a pure length perspective, there's zero wasted verbiage. Every word earns its place, though there are too few words to be helpful.

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 (8 parameters with enums, no annotations, no output schema, 0% schema description coverage), the description is completely inadequate. It doesn't explain what a review is, what the parameters mean, what the tool returns, or any behavioral aspects. For a creation tool with this level of schema complexity, the description fails to provide essential context.

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 description provides zero information about any of the 8 parameters. With 0% schema description coverage, the schema only shows data types and constraints without explaining what each parameter means. The description doesn't compensate at all - it doesn't mention user_id, review fields, ratings, or status codes that appear 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 'Create a review' is a tautology that merely restates the tool name without providing any meaningful context about what a review entails or what resource it operates on. While it includes a verb ('Create'), it lacks specificity about the resource being created and doesn't distinguish this tool from its many sibling 'create' tools (like createUser, createPost, etc.).

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 about when to use this tool versus alternatives. There's no mention of prerequisites, appropriate contexts, or comparisons to sibling tools like 'updateReview' or 'getReview'. The agent must infer usage entirely from the tool name and schema.

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