brilliant-directories-mcp

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

With no annotations provided, the description fails to disclose critical behavioral traits. It doesn't indicate that this is a destructive operation, specify permission requirements, mention side effects (e.g., cascading deletions), or describe the response format. For a mutation tool with zero annotation coverage, this is a severe gap.

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?

While concise with three words, the description is under-specified rather than efficiently structured. It lacks front-loaded critical information and fails to earn its place by adding value beyond the tool name, making it ineffective despite its brevity.

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?

The description is incomplete given the tool's complexity as a destructive operation. With no annotations, no output schema, and minimal description, it doesn't prepare the agent for safe or effective use. Sibling tools include many delete operations, but no differentiation is provided.

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 100%, with the single parameter 'seo_id' documented as 'Page primary key'. The description adds no additional parameter information beyond what the schema provides, so it meets the baseline of 3 where the schema handles the documentation burden.

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 'Delete a page' restates the tool name with minimal elaboration, making it tautological. It specifies the verb 'delete' and resource 'page' but doesn't distinguish this from other delete operations like deletePost or deleteCategory, nor does it clarify what constitutes a 'page' in this context.

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. There's no mention of prerequisites (e.g., needing a page ID), exclusions, or comparisons with sibling tools like deletePost or deleteCategory, leaving the agent without context for selection.

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