Ops 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 clearly indicates this is a state-changing operation (unpausing affects DAG scheduling) and specifies the return value ('confirmation of the unpause action'), though it doesn't detail error conditions or side effects like impact on existing runs.

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 efficiently structured with a clear purpose statement, parameter explanations in a labeled 'Args' section, and a returns statement. Every sentence adds value, with no wasted words, and important warnings are front-loaded with 'IMPORTANT'.

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 moderate complexity (state change with environment targeting), no annotations, and the presence of an output schema (implied by 'Returns confirmation'), the description is complete. It covers purpose, parameters with constraints, usage warnings, and return value, leaving no gaps for the agent to operate effectively.

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 0%, so the description must fully compensate. It provides essential semantic context for both parameters: 'dag_id' is explained as 'The DAG to unpause', and 'env' includes detailed constraints ('Target environment — 'dev', 'uat', 'test', or 'prod'') and critical usage warnings, adding significant value beyond the bare 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 specific action ('unpause a DAG') and the effect ('allows scheduled runs to trigger again'), which distinguishes it from sibling tools like 'pause_dag'. It uses precise verb+resource language without being tautological.

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 guidance on when to use this tool (to resume scheduled DAG runs) and includes critical usage instructions for the 'env' parameter ('IMPORTANT: Do NOT guess or default. Ask the user which environment if not specified'), which helps differentiate it from alternatives and prevents misuse.

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