Aedifion MCP Server

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

No annotations are provided, so the description carries the full burden. While 'Delete' implies destruction, there is no disclosure about whether this is permanent, if it requires confirmation, affects active ai_chat sessions, or specific permissions needed given the destructive nature.

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 core action is front-loaded in the first sentence. The 'Args:' section is somewhat unconventional for MCP (typically belonging in schema descriptions) but is efficient. No extraneous information is included.

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 single-parameter destructive operation with an output schema present, the description is minimally adequate but lacks safety context. It does not address irreversibility, cascading effects, or the relationship to ongoing conversations that would help an agent invoke this safely.

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 0% schema description coverage, the description minimally compensates by stating thread_id is 'The thread identifier.' This is tautological but provides the only semantic layer beyond the schema. It does not explain format constraints, examples, or how to obtain valid thread IDs.

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 a specific verb ('Delete') and resource ('AI conversation thread'), clearly distinguishing it from sibling tools like ai_chat (interact), ai_get_thread (retrieve), and ai_get_threads (list).

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, prerequisites (e.g., whether the thread must be inactive), or warnings about irreversibility.

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