Aedifion MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions pagination parameters which implies a list operation with potential result limits, but doesn't describe what 'alerts' consist of, whether the operation is safe/read-only, authentication requirements, rate limits, error conditions, or the structure of returned data. The description is minimal beyond stating the basic operation.

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 efficiently structured with a clear purpose statement followed by parameter explanations. Every sentence serves a purpose with minimal waste. The formatting with 'Args:' section makes it scannable, though the parameter explanations could be slightly more informative.

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 that there's an output schema (which handles return values), no annotations, and moderate complexity (3 parameters with 0% schema coverage), the description provides the minimum viable information. It states what the tool does and documents parameters, but lacks behavioral context, usage guidance, and richer parameter semantics that would be helpful for an AI agent.

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 provides parameter names and brief explanations ('The project's numeric ID', 'Page number', 'Items per page'), which adds basic semantic meaning beyond the schema's type information. However, it doesn't explain valid ranges, constraints, or practical usage details for the pagination parameters (like typical page sizes or what 'null' means for defaults).

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 action ('Get all alerts') and resource ('configured in a project'), making the purpose immediately understandable. However, it doesn't explicitly differentiate this tool from potential siblings like 'get_analytics_instance' or 'get_controls_instance' that might also retrieve alert-related data, though those appear to be for different resource types.

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. While there are sibling tools like 'create_threshold_alert', 'delete_alert', 'disable_alert', and 'enable_alert' that manage alerts, the description doesn't mention these relationships or provide context about when retrieval versus modification is appropriate.

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