Context Engine 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 describes a read-only discovery operation, which implies non-destructive behavior, but does not detail aspects like response format, potential errors, or any server-specific constraints. This leaves gaps in understanding how the tool behaves beyond its basic purpose.

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 a single, efficient sentence: 'Discover available tools and capabilities exposed by the server.' It is front-loaded with the core purpose, has zero waste, and is appropriately sized for a tool with no parameters. Every word contributes to clarity without redundancy.

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 tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It explains what the tool does but lacks details on behavioral traits or output, which could be important for discovery operations. With no output schema, it should ideally hint at return values, but it does not, leaving some contextual gaps.

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 has 0 parameters with 100% coverage, meaning no parameters are documented. The description does not add parameter details, which is appropriate since there are none to explain. It effectively compensates by focusing on the tool's function without unnecessary parameter information, aligning with the schema's completeness.

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: 'Discover available tools and capabilities exposed by the server.' It uses specific verbs ('Discover') and resources ('tools and capabilities'), making the intent unambiguous. However, it does not explicitly differentiate this from sibling tools, which might include other informational or discovery tools, though none are listed among siblings.

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 implies usage context by stating it discovers tools and capabilities, suggesting it should be used to explore what the server offers. However, it provides no explicit guidance on when to use this tool versus alternatives, such as checking for specific tool details or during setup phases. The context is clear but lacks exclusions or named alternatives.

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