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. 'Update a widget' implies a mutation operation but doesn't specify permissions required, whether changes are reversible, rate limits, error conditions, or what the response contains. This leaves critical behavioral aspects undocumented.

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 three words, making it front-loaded and free of unnecessary verbiage. However, this conciseness comes at the cost of being under-specified rather than efficiently informative.

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?

For a mutation tool with three parameters, 0% schema coverage, no annotations, and no output schema, the description is completely inadequate. It doesn't address behavioral traits, parameter meanings, usage context, or expected outcomes, leaving the agent with insufficient information to use the tool correctly.

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%, meaning none of the three parameters (widget_id, widget_name, widget_data) are documented in the schema. The description adds no parameter information whatsoever—it doesn't explain what these parameters mean, their formats, or how they interact. This fails to compensate for the complete lack of schema documentation.

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 'Update a widget' is a tautology that merely restates the tool name without adding meaningful context. It specifies the verb ('update') and resource ('widget'), but doesn't distinguish this tool from sibling update tools like updateCategory or updateUser, nor does it clarify what aspects of a widget can be updated.

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. There are multiple sibling update tools (e.g., updateCategory, updateUser), but no indication of when updateWidget is appropriate, what prerequisites exist, or what distinguishes it from other update operations.

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