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 'Delete an alert', implying a destructive mutation, but fails to describe critical traits: whether deletion is permanent, requires specific permissions, has side effects (e.g., on related data), or returns confirmation. This is inadequate for a mutation tool with zero annotation coverage.

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 brief and front-loaded with the core purpose ('Delete an alert.'), followed by parameter details. It avoids unnecessary words, but the 'Args' section could be integrated more smoothly. 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 this is a destructive mutation tool with no annotations, 0% schema description coverage, and an output schema (which might help), the description is insufficient. It lacks behavioral details, usage context, and parameter semantics beyond a basic label, failing to compensate for the missing structured information.

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 description includes an 'Args' section that documents the single parameter 'alert_id', adding meaning beyond the input schema, which has 0% description coverage. However, it only states 'The alert ID' without explaining format, source, or validation rules. With one parameter and low schema coverage, this provides basic but incomplete semantic context.

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 verb 'Delete' and the resource 'an alert', making the purpose unambiguous. It distinguishes this as a deletion operation, which is different from sibling tools like 'disable_alert' or 'create_threshold_alert'. However, it doesn't specify what type of alert (e.g., threshold alert) or from what context (e.g., project), which prevents a perfect 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 like 'disable_alert' or other deletion tools (e.g., 'delete_project', 'delete_task'). It lacks context about prerequisites, such as whether the alert must be disabled first or if deletion is irreversible, leaving the agent without usage instructions.

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