Context Engine MCP Server

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

With no annotations provided, the description carries the full burden. It discloses that the tool pauses a session (implying mutation) and can be resumed, but lacks details on permissions, side effects (e.g., state persistence), or error handling. It adds some context (e.g., freeing resources) but doesn't fully compensate for the absence of annotations.

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 core purpose in the first sentence, followed by a concise alternative and a bulleted list of use cases. Every sentence earns its place without redundancy, making it efficient and well-structured.

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 complexity (a mutation tool with no annotations and no output schema), the description is adequate but has gaps. It explains the purpose and usage well but lacks details on behavioral traits (e.g., what 'pause' entails operationally) and doesn't cover return values, leaving room for improvement 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 schema description coverage is 100%, so the schema already documents the 'session_id' parameter. The description doesn't add specific parameter details beyond implying it targets a session, but with 0 parameters needing extra explanation, it meets the baseline of 4 for minimal parameter burden.

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 specific action ('pause') and target resource ('a running reactive review session'), distinguishing it from siblings like 'resume_review' (for resuming) and 'get_review_status' (for checking status). It avoids tautology by not merely restating the tool name.

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?

It explicitly states when to use this tool ('pause a running reactive review session') and provides an alternative ('resume_review' for resuming later). The 'useful for' section gives concrete scenarios (freeing resources, manual intervention, stopping before problematic steps), offering clear guidance on appropriate contexts.

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