Get Server Capabilities

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

Beyond annotations that mark it as a safe, read-only, idempotent operation, the description details the exact content returned for each detail level, including tools list, call signatures, error taxonomy, and vocabularies. This provides rich behavioral context beyond what annotations alone convey.

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?

Every sentence in the description serves a purpose: stating the tool's output, detailing parameter options, providing usage guidance, and giving the signature. It is tightly written with no redundancy, making it concise yet comprehensive.

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 parameter count (1), full schema coverage, presence of output schema, and the tool's nature as a discovery surface, the description leaves no gaps. It covers what the tool returns, how to use it, and when to call it, fully equipping the agent.

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 input schema already has 100% coverage with a clear enum, but the description adds significant meaning by explaining what each value yields ('summary' vs 'full') and even provides the call signature. This enriches the agent's understanding beyond the schema's minimal descriptions.

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 it returns the 'mgi-link discovery surface' with two detail levels ('summary' and 'full'), specifying exactly what each includes. It distinguishes this meta-tool from sibling tools that deal with markers or phenotypes, making its unique purpose explicit.

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 explicitly advises 'Call this first in a cold session,' providing clear context for initial use. It also offers an alternative method ('read mgi://tools / mgi://capabilities'), effectively guiding when to use the tool versus other means.

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