brilliant-directories-mcp

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

With no annotations provided, the description carries full burden but offers no behavioral details. It doesn't disclose that this is a destructive operation, potential side effects (e.g., cascading deletions), authentication needs, error conditions, or response format, leaving critical behavioral traits unspecified.

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, 'Delete a post type', which is front-loaded and wastes no words. However, this brevity comes at the cost of completeness, but strictly for conciseness, it scores perfectly.

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 destructive nature (implied by 'Delete'), no annotations, 0% schema coverage, no output schema, and multiple sibling tools, the description is severely incomplete. It lacks essential context like behavioral risks, parameter meaning, and usage guidelines, making it inadequate for safe and effective tool invocation.

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%, and the description adds no parameter information. It doesn't explain what 'data_id' represents (e.g., an identifier for the post type), its format, or constraints, failing to compensate for the 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 'Delete a post type' restates the tool name with minimal elaboration, making it tautological. It specifies the verb ('Delete') and resource ('a post type'), but lacks differentiation from sibling delete tools (e.g., deletePost, deleteCategory) or details on what 'post type' entails, leaving purpose vague beyond the obvious.

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. It doesn't mention prerequisites (e.g., needing an existing post type), exclusions, or comparisons with related tools like deletePost or updatePostType, offering no contextual direction for the agent.

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