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 only implies read-only safety via 'Get' but doesn't disclose error behaviors (e.g., what happens if project_id or cip_id is invalid), rate limits, or performance characteristics.

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?

Extremely terse at three lines. The Args block is clear and efficient, though slightly formal. No redundant or wasted text, though the formatting could integrate better with the single sentence description.

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 output schema exists, it doesn't need to describe return values. The two parameters are documented in the description text. However, given the rich set of sibling tools (get_component_pins, get_component_attribute_definitions), the description should clarify what constitutes an 'attribute' versus other component data.

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 description compensates adequately by documenting both parameters: clarifying project_id as 'numeric ID' and defining cip_id as 'component-in-project ID' (expanding the acronym).

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 action ('Get') and resource ('attributes of a component') with clear scope ('in a project'). However, it doesn't differentiate well from siblings like get_project_component (the component itself) vs get_component_attribute_definitions (the schema for attributes).

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 this versus related tools like get_component_pins, get_component_results, or get_project_component. No mention of prerequisites or error conditions.

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