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. It states 'Get' which implies a read-only operation, but doesn't specify if it requires authentication, has rate limits, or what the return format looks like. This leaves significant gaps in understanding the tool's behavior.

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 click record', which is front-loaded and wastes no words. Every part of the sentence contributes to the core purpose, making it efficient and well-structured.

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 low complexity (1 parameter) but lack of annotations and output schema, the description is incomplete. It doesn't explain what a 'click record' contains, how it's retrieved, or any error conditions, leaving the agent with insufficient context to use the tool 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 description adds no parameter semantics beyond the input schema, which has 0% description coverage. However, with only one required parameter ('click_id'), the tool is simple, and the description's lack of param details is less critical. The baseline for 0 parameters would be 4, but here there is 1 parameter, so it's slightly penalized.

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 'Get a single click record' clearly states the verb 'Get' and resource 'click record', indicating a retrieval operation. However, it lacks specificity about what a 'click record' entails and doesn't differentiate from sibling tools like 'listClicks' or 'updateClick', making it somewhat vague.

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 'listClicks' for multiple records or 'updateClick' for modifications. The description implies usage for retrieving a single record but offers no context on prerequisites, exclusions, or comparisons to other tools.

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