Aedifion MCP Server

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

No annotations provided, so description carries full burden. Mentions 'check availability' indicating read-only nature, but lacks disclosure of auth requirements, rate limits, timeout behavior, or what specific availability metrics are returned despite output schema existing.

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?

Single sentence, immediately front-loaded with action and purpose. No redundant phrases or wasted words. Appropriate length for zero-parameter tool.

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?

Sufficient for tool complexity: zero inputs, output schema exists to document return values. Description covers core intent. Lacks only operational details (timeout, retry behavior) that would make it fully comprehensive given no annotations.

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?

Zero parameters per schema, which per guidelines establishes baseline of 4. Description correctly implies no configuration needed for a ping operation, consistent with the empty properties object.

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?

Description uses specific verb 'Ping' with specific target 'aedifion API server' and specific outcome 'check availability'. Clear distinction from siblings like get_api_version or get_endpoints which retrieve data rather than test connectivity.

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?

Implies usage context (checking availability) but lacks explicit guidance on when to use versus other status-checking tools like get_api_version or get_analytics_status. No mention of prerequisites or typical calling patterns.

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