Aedifion MCP Server

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

No annotations provided, so description carries full burden, yet it only states 'Get' implying read-only safety without describing what data is returned, error conditions, or whether this triggers any background processing.

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?

Brief and front-loaded, but the Args docstring format is unusual for MCP and the brevity squanders opportunity to address behavioral gaps given zero annotation coverage.

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?

Simple single-parameter tool, but lacks output schema description, rate limit warnings, or domain context needed to navigate the dense sibling analytics toolset (instances, KPIs, components).

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?

With 0% schema description coverage, the Args section successfully adds critical semantics: 'project_id' is 'The project's numeric ID', clarifying ownership and format beyond the schema's bare 'Project Id' title.

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?

States specific verb 'Get' and resource 'analytics status overview', but 'overview' is vague and fails to distinguish from sibling 'get_analytics_instance_status', which appears to be instance-level versus this project-level scope.

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?

Provides no guidance on when to use this versus alternatives like 'get_analytics_instance_status' or 'get_project'. No mention of prerequisites or when not to use.

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