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 of behavioral disclosure. It states the tool 'Get[s] all messages,' implying a read-only operation, but doesn't clarify permissions, rate limits, pagination, or error handling. For a tool with no annotation coverage, this is insufficient to ensure safe and effective use.

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 concise and front-loaded, with the main purpose stated first. The additional 'Args' section is brief and relevant. However, the second sentence could be integrated more smoothly, and there's slight redundancy in stating the parameter name twice, but overall it's efficient with minimal waste.

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 has an output schema (which handles return values) and only one parameter, the description is somewhat complete. However, with no annotations and low schema coverage, it lacks behavioral context and detailed parameter guidance. It's adequate for a simple read operation but misses opportunities to clarify usage and constraints.

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 schema description coverage is 0%, meaning the input schema lacks descriptions for parameters. The description adds a brief note: 'thread_id: The thread identifier,' which provides basic semantics but lacks details like format, source, or constraints. Since there's only one parameter, the baseline is 4, but the minimal explanation reduces it to 3, as it doesn't fully compensate for the schema gap.

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 tool's purpose: 'Get all messages in an AI conversation thread.' It specifies the verb ('Get') and resource ('messages in an AI conversation thread'), making it easy to understand. However, it doesn't explicitly differentiate from its sibling 'ai_get_threads' (which likely lists threads rather than messages within a thread), so it misses the highest score.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing thread_id), exclusions, or comparisons with related tools like 'ai_get_threads' or 'ai_chat'. This leaves the agent without context for tool selection.

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