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. It reveals the tool's wrapper nature and automatic selection logic, which is valuable behavioral context. However, it doesn't describe what the tool actually does after selection (presumably invokes the chosen tool), nor does it mention error handling, performance characteristics, or other behavioral traits. The description adds some value but leaves significant gaps.

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 and well-structured in a single sentence that efficiently communicates the tool's core functionality. Every word earns its place by explaining the wrapper nature, decision logic, and tool alternatives. There's no wasted text 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?

Given the tool's complexity as a wrapper with 8 parameters and no output schema, the description is somewhat incomplete. It explains the selection logic but doesn't describe what happens after selection, what the tool returns, or how errors are handled. With no annotations and no output schema, more behavioral context would be helpful for a tool that orchestrates other tools.

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 8 parameters thoroughly. The description doesn't add any parameter-specific information beyond what's in the schema. It mentions the 'diff' parameter implicitly in the decision logic but doesn't provide additional semantics. The baseline score of 3 is appropriate when the schema does all the parameter documentation work.

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 as a 'smart wrapper' that automatically chooses between two specific sibling tools (review_diff and review_git_diff) based on input conditions. It explicitly names both alternatives and specifies the decision logic (chooses review_diff when a diff is provided, otherwise chooses review_git_diff for the current git workspace), providing excellent differentiation from 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 provides explicit usage guidelines by stating when each tool is selected: 'chooses review_diff when a diff is provided; otherwise chooses review_git_diff for the current git workspace.' This gives clear decision rules for the automatic mode and distinguishes between the two scenarios, though it doesn't mention when to use this wrapper versus directly calling the underlying tools.

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