Aedifion MCP Server

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

No annotations are provided, so the description carries full burden. 'Enable' implies a state-changing mutation, but the description doesn't disclose behavioral traits like what 'enabling' actually does (e.g., starts monitoring, sends notifications), whether it requires specific permissions, if it's reversible via disable_alert, or what happens on success/failure. For a mutation tool with zero annotation coverage, this is inadequate.

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 ('Enable an alert'), followed by a basic parameter note. There's no wasted text, though the under-specification might stem from excessive conciseness rather than efficiency. The two-sentence structure is clear.

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 1 parameter, no annotations, but an output schema exists, the description is minimally complete but lacks depth. The output schema may cover return values, but the description doesn't address key context like what 'enabling' entails, error conditions, or relations to sibling tools. It's borderline adequate for a simple tool but misses mutation-specific details.

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 only states 'alert_id: The alert ID', which adds minimal meaning beyond the schema's 'Alert Id' title. It doesn't explain format constraints, where to find alert IDs, or valid ranges. With 1 parameter at 0% coverage, this leaves the parameter poorly documented.

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 'Enable an alert' is a tautology that restates the tool name without adding specificity. It doesn't explain what 'enabling' means operationally (e.g., activating monitoring, resuming notifications) or what resource is affected beyond the generic 'alert'. This provides minimal value beyond the tool name itself.

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 about when to use this tool versus alternatives. The sibling list includes 'disable_alert', 'create_threshold_alert', 'delete_alert', and 'update_threshold_alert', but the description doesn't differentiate this from those related tools or explain prerequisites (e.g., requires an existing alert, might conflict with disabled state).

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