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 'Get[s] a specific component,' implying a read-only operation, but does not specify permissions needed, rate limits, error handling, or what 'Get' entails (e.g., returns metadata, full details). For a tool with no annotations, this is a significant gap in transparency.

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 front-loaded with the purpose in the first sentence, followed by parameter explanations. It is appropriately sized with no redundant information, though the parameter section could be more integrated. Every sentence earns its place, but the structure is slightly fragmented.

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 an output schema exists, the description does not need to explain return values. However, with no annotations, 0% schema description coverage, and two parameters, the description provides basic purpose and parameter semantics but lacks behavioral context and usage guidelines. It is minimally adequate but has clear gaps for a read operation tool.

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%, so the description must compensate. It adds meaning by explaining 'project_id: The project's numeric ID' and 'cip_id: The component-in-project ID,' clarifying what these IDs represent beyond the schema's basic types. However, it does not provide format examples or constraints, leaving some ambiguity.

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 a specific component in a project.' It uses a specific verb ('Get') and resource ('component in a project'), but does not differentiate from sibling tools like 'get_project_components' (plural) or 'get_components' (general). This makes it clear but not fully distinguished from alternatives.

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 is provided on when to use this tool versus alternatives such as 'get_project_components' or 'get_components'. The description only states what it does, without context on prerequisites, exclusions, or comparison to siblings. This leaves the agent to infer usage from the tool name alone.

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