Aedifion MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a chat message sending operation but doesn't describe what happens after sending (e.g., does it return a response immediately? is it asynchronous?), authentication requirements, rate limits, or error conditions. The mention of thread management ('new' for new thread) adds some context but insufficient for a mutation tool.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence serves a purpose with zero wasted words. The two-sentence format with parameter details in a structured Args section is appropriately front-loaded and concise.

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 that this is a mutation tool with no annotations but has an output schema, the description is moderately complete. It explains the core action and parameters adequately, and the output schema will handle return values. However, for an AI chat tool, more context about the assistant's capabilities, response format, or typical use cases would be helpful given the complexity of AI interactions.

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%, so the description must compensate. It provides clear documentation for both parameters: 'thread_id' with the special value 'new' for new threads, and 'message' as the content to send. This adds meaningful semantics beyond the bare schema, though it doesn't elaborate on thread persistence, message formatting, or length limits.

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 clearly states the action ('Send a chat message') and target ('to the aedifion AI assistant'), making the purpose understandable. It distinguishes from siblings by focusing on AI chat functionality rather than project/task management or data operations. However, it doesn't specify what kind of responses to expect or the assistant's capabilities.

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 implies usage for interacting with an AI assistant, but provides no explicit guidance on when to use this versus other tools. The parameter documentation mentions 'use 'new' for a new thread' which gives some implementation context, but doesn't address use cases, prerequisites, or alternatives among the many sibling tools.

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