Aedifion MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states this is a list operation, implying read-only behavior, but doesn't mention authentication requirements, rate limits, error conditions, or what the output contains. The pagination parameters are mentioned but without explaining default behavior or constraints.

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 appropriately concise with a clear purpose statement followed by parameter explanations. The two-sentence structure is efficient, though the parameter explanations could be integrated more smoothly rather than as a separate 'Args:' section.

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 read-only list tool with 2 optional parameters and an output schema (which handles return values), the description provides adequate basic information. However, with no annotations and 0% schema description coverage, it should ideally explain more about authentication context, pagination defaults, and what 'AI conversation threads' specifically means in this system.

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 schema provides no parameter descriptions. The description adds basic semantic meaning by identifying 'page' and 'per_page' as pagination parameters, which is helpful. However, it doesn't explain acceptable ranges, default values, or what happens when parameters are null (as allowed by the schema).

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 with a specific verb ('List') and resource ('all AI conversation threads for the current user'). It distinguishes from sibling 'ai_get_thread' (singular) by indicating it retrieves multiple threads. However, it doesn't explicitly differentiate from other list-style tools like 'get_logbooks' or 'get_analytics_instances' beyond the resource type.

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. While it's clear this lists AI threads, there's no mention of prerequisites, when to use pagination parameters, or how it relates to other thread management tools like 'ai_delete_thread' or 'ai_chat'.

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