Aedifion MCP Server

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

With no annotations provided, the description carries full disclosure burden but provides minimal behavioral context. No mention of permissions required, whether creation is synchronous, validation rules for the JSON config, or side effects.

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. The Args section is necessary given zero schema coverage and efficiently delivers the required parameter semantics without redundancy.

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?

Inadequate for a creation tool with lifecycle implications (see siblings delete_analytics_instance, disable_analytics_instance). Missing: config structure details, relationship to update_analytics_instance, and whether output schema contains the created instance ID.

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%, requiring the description to compensate. It adds type context ('numeric ID', 'JSON string') for both parameters beyond the schema's titles, though instance_config lacks structural details.

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?

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 when/when-not guidance provided. Does not mention prerequisite steps (e.g., needing a project_id first) or distinguish from sibling tools like create_controls_instance or create_plot_view.

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