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 of behavioral disclosure and does so effectively. It explains critical behavioral traits: default preview-only execution (apply_changes=false), failure handling (stop_on_failure=true), dependency-aware execution, and progress tracking. It also mentions the ability to load saved plans via plan_id. The only minor gap is lack of explicit mention about permissions or rate limits.

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 well-structured and appropriately sized. It begins with a clear purpose statement, then organizes information into logical sections (Execution Modes, Output, Important notes). Every sentence adds value - there's no redundant or unnecessary information. The bullet points make key information easily scannable.

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 complex tool with 8 parameters, no annotations, and no output schema, the description does an excellent job of providing context. It explains execution modes, output format, critical behavioral defaults, and parameter relationships. The only gap is that without an output schema, the description could provide more detail about the exact structure of the returned data (though it does list what information will be included).

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 baseline is 3. The description adds some value by explaining the relationship between mode and step_number ('single_step: Execute a specific step by number (requires step_number)'), clarifying the plan/plan_id alternative ('You can pass a saved plan_id instead of the full plan JSON'), and emphasizing the default behavior of apply_changes. However, it doesn't provide significant additional semantics beyond what's already well-documented in the schema.

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: 'Execute steps from an implementation plan, generating code changes.' It specifies the verb ('execute'), resource ('steps from an implementation plan'), and outcome ('generating code changes'), distinguishing it from sibling tools like create_plan, refine_plan, or visualize_plan which handle planning rather than execution.

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 clear context for usage through the 'Execution Modes' section, explaining when to use single_step, all_ready, or full_plan modes. It mentions alternatives like using plan_id instead of plan JSON. However, it doesn't explicitly state when NOT to use this tool or compare it directly to sibling tools like complete_step or start_step.

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