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. While 'Create an approval request' implies a write/mutation operation, the description doesn't address critical aspects like permissions needed, whether this triggers notifications, what happens if approval is already pending, or the expected response format. This leaves significant gaps for an agent to understand the tool's behavior.

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 that directly states the tool's purpose without any redundant information. It's appropriately sized and front-loaded, with every word contributing to understanding the core functionality.

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 of an approval request tool (likely involving workflow state changes), the absence of annotations, and no output schema, the description is insufficient. It doesn't cover behavioral traits, error conditions, or return values, leaving the agent with inadequate information to use this tool effectively in context with its siblings.

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%, with both parameters ('plan_id' and 'step_numbers') clearly documented in the schema. The description adds minimal value beyond the schema by mentioning 'plan or specific steps', which loosely corresponds to the parameters but doesn't provide additional syntax, format details, or usage examples. This meets the baseline for high schema coverage.

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 ('Create an approval request') and the target ('for a plan or specific steps'), which provides a specific verb+resource combination. However, it doesn't explicitly differentiate this tool from sibling tools like 'respond_approval' or 'get_review_status', which appear related to approval workflows.

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 are multiple sibling tools related to plans, approvals, and reviews (e.g., 'respond_approval', 'get_review_status', 'review_auto'), but the description offers no context about prerequisites, appropriate scenarios, or exclusions.

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