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 the operation but fails to disclose mutation characteristics, side effects, permissions required, or what happens if the user isn't currently assigned (error vs silent success).

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?

Appropriately brief with no filler sentences. The Args block is structured clearly, and given the 0% schema coverage, its inclusion is necessary rather than wasteful.

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?

Although the tool has only two simple parameters and an output schema exists, the description misses critical safety context for a mutation operation. Without annotations or behavioral notes, the agent cannot assess the impact of calling this tool.

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%, requiring heavy description compensation. The Args block provides only 'The task ID' (redundant with title) and 'The user ID to unassign' (minimal semantic addition). It lacks format constraints, ID sources, or whether these are internal vs external 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?

Provides a specific verb ('Unassign') and resource ('task') with clear scope ('from a user'). However, it does not explicitly differentiate from sibling tool 'assign_task' or clarify when to use unassignment versus reassignment.

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?

Contains no guidance on when to use this tool versus alternatives, prerequisites (e.g., task must currently be assigned to the user), or failure modes. The agent has no signal for whether this is safe to call idempotently.

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