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. It states 'Get a single category' but doesn't disclose behavioral traits such as whether this is a read-only operation, what happens if the category_id doesn't exist (e.g., error vs. null), authentication requirements, rate limits, or response format. The description is too minimal to inform the agent adequately about how the tool behaves.

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 a single sentence ('Get a single category'), which is front-loaded and wastes no words. For a simple tool, this brevity is appropriate, though it may sacrifice completeness.

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 simplicity (1 parameter, no output schema, no annotations), the description is incomplete. It doesn't explain what 'Get' returns (e.g., category details), how to handle errors, or differentiate from siblings. For a tool in a context with many alternatives, more context is needed to guide the agent effectively.

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 input schema has 1 parameter (category_id) with 0% description coverage, meaning the schema provides no semantic context. The description adds no information about the parameter, such as what a category_id represents, valid ranges, or examples. This leaves the parameter's meaning ambiguous beyond its type (integer).

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 states the verb ('Get') and resource ('a single category'), which clarifies the basic purpose. However, it doesn't distinguish this tool from its sibling 'listCategories' (which likely returns multiple categories) or specify what 'Get' entails (e.g., retrieve details vs. just existence). The purpose is clear but lacks differentiation from alternatives.

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 like 'listCategories' or other 'get' tools for different resources. There's no mention of prerequisites, context, or exclusions. The agent must infer usage solely 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.