brilliant-directories-mcp

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Create a widget' implies a write/mutation operation but provides no information about permissions required, whether creation is idempotent, what happens on failure, or what the response contains. This is inadequate 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 maximally concise at just two words. While this represents under-specification rather than ideal conciseness, it contains no redundant information and is properly front-loaded with the core action.

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 4 parameters, 25% schema coverage, no annotations, and no output schema, the description is completely inadequate. It provides no behavioral context, no parameter guidance, no usage differentiation from siblings, and no information about what constitutes successful widget creation or what gets returned.

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?

With only 25% schema description coverage (only 'widget_data' has a description), the description adds no parameter information beyond what's in the schema. It doesn't explain what 'widget_name' represents, clarify the meaning of 'widget_viewport' enum values, or indicate what 'bootstrap_enabled' controls. The description fails to compensate for the low schema coverage.

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 widget' is a tautology that restates the tool name without adding specificity. It doesn't explain what a widget is in this context or what resources it creates, nor does it differentiate from sibling tools like 'createCategory' or 'createPage' which follow the same naming pattern.

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. With many sibling 'create' tools available (createCategory, createPage, createUser, etc.), there's no indication of what distinguishes widget creation from other resource creation operations or when this specific tool is appropriate.

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