Aedifion MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to mention idempotency, side effects, error conditions, or the structure of the return value despite confirmation that an output schema exists. It provides no context regarding whether adding a component triggers cascading operations, requires specific permissions, or validates against existing definitions.

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 appropriately brief with the primary action statement front-loaded, followed by a structured Args section that documents parameters efficiently without excessive verbosity. The two-line structure minimizes waste while conveying essential invocation context, though the docstring-style formatting is slightly informal.

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 the simple two-parameter schema and existence of an output schema, the description adequately covers parameter identification through the Args block but remains incomplete regarding behavioral prerequisites, side effects, and mutation consequences necessary for robust agent decision-making.

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?

Despite 0% schema description coverage (only titles provided), the Args section provides crucial semantic clarification that 'component_id' refers specifically to a 'component definition ID' rather than an instance identifier, and confirms 'project_id' is numeric. This successfully compensates for the schema's generic titles by clarifying that the component parameter references a predefined definition rather than an arbitrary value.

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 states the specific action 'Add' and target resource 'a component to a project,' clearly distinguishing it from sibling tools like 'delete_project_component' and 'get_project_components' through verb choice. However, it lacks domain-specific clarity regarding what constitutes a 'component' in this system (e.g., whether it's a device, module, or configuration element) given the presence of related component definition and attribute tools among siblings.

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 explicit guidance on when to use this tool versus alternatives, prerequisites such as component definition creation or project existence, or conditions where the operation might fail. There is no indication of whether the component definition must already exist in the system or how this relates to the 'get_components' or 'get_component_attribute_definitions' workflows suggested by sibling tools.

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