Aedifion MCP Server

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

No annotations provided, yet description fails to disclose mutation safety, rate limits, pagination behavior, or data freshness. Only format hint is ISO 8601 for timestamps, leaving significant behavioral gaps.

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?

Compact Args-section format efficiently documents four parameters without verbosity, though the docstring style is slightly inconsistent with typical MCP prose descriptions.

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?

Lacking output schema, annotations, and any explanation of what 'operational optimization data' contains (metrics? recommendations? historical?), the description is insufficient for a 4-parameter data retrieval tool in a complex industrial/IoT domain.

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 partially compensates by noting project_id is 'numeric' and time fields use 'ISO 8601 format.' However, 'Unit system' is tautological and provides no valid values (metric/imperial) or 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?

States it retrieves 'operational optimization data for a project' with clear verb (Get) and scope (project), but 'operational optimization' remains vague and doesn't differentiate from siblings like get_energy_efficiency or get_technical_monitoring.

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 on when to use versus alternatives (e.g., when to choose this over get_analytics_kpi_overview), nor any mention of prerequisites or constraints beyond the Args list.

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