Context Engine MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'deterministically' and '(no LLM)' which provide some implementation context, but doesn't describe what happens during execution (e.g., what constitutes an invariant violation, how results are presented, whether it modifies anything, or error handling). For a tool with 3 parameters and no annotation coverage, this is insufficient.

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 extremely concise - a single sentence with a parenthetical clarification. Every word serves a purpose: 'Run' (action), 'YAML invariants' (what), 'deterministically' (how), 'against a unified diff' (target), '(no LLM)' (implementation constraint). No wasted words or 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?

For a tool with 3 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what YAML invariants are, what constitutes success/failure, what the output looks like, or how this tool fits into the broader code review workflow with sibling tools. The 100% schema coverage helps with parameters, but behavioral context is missing.

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 100%, so the schema already documents all parameters thoroughly. The description doesn't add any meaningful parameter semantics beyond what's in the schema - it mentions 'unified diff' and 'YAML invariants' which align with parameter names but don't provide additional context about format, constraints, or relationships between parameters.

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 action ('Run YAML invariants deterministically') and the target ('against a unified diff'), with the parenthetical '(no LLM)' providing additional specificity about implementation. However, it doesn't explicitly differentiate from sibling tools like 'review_diff' or 'run_static_analysis' that might have overlapping functionality.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, typical use cases, or comparison to sibling tools like 'review_diff' or 'run_static_analysis' that might serve similar purposes in the code review context.

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