Aedifion MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool is a 'Get' operation, implying it is read-only, but does not specify any behavioral traits such as permissions required, rate limits, pagination, or what happens if the component_id is invalid. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior.

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 concise and well-structured, with a clear purpose statement followed by parameter details in a separate section. There is no unnecessary information, and it is front-loaded with the main functionality. It could be slightly improved by integrating the parameter explanation more seamlessly, but it is efficient overall.

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 that there is an output schema (as indicated by context signals), the description does not need to explain return values. However, with no annotations, one parameter, and low schema coverage, the description provides basic purpose and parameter semantics but lacks usage guidelines and behavioral details. It is adequate for a simple read tool but has clear gaps in completeness.

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?

The description includes an 'Args' section that explains the 'component_id' parameter as 'The component definition ID.' This adds meaning beyond the input schema, which has 0% description coverage and only provides a title and type. However, with only one parameter, the baseline is high, and the explanation is minimal, so it meets but does not exceed basic expectations.

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 clearly states the tool's purpose: 'Get all pins and their attributes for a component type.' It specifies the verb ('Get'), resource ('pins and their attributes'), and scope ('for a component type'). However, it does not explicitly distinguish this tool from its sibling 'get_component_pins', which appears to be a similar tool, so it misses full differentiation.

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 guidance on when to use this tool versus alternatives. It does not mention any prerequisites, exclusions, or related tools like 'get_component_pins' from the sibling list. The only context is the parameter explanation, which is insufficient for usage decisions.

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