Check ci lifecycle compat actions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that, however: it never explains what 'compatible' means, what a violation looks like, or whether any state is consulted or mutated remotely.

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?

A single clean sentence with no filler, and the purpose is front-loaded. It is well formed but under-specified rather than deliberately concise.

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?

There is no output schema and the input schema is a bare passthrough with no descriptions, so the description carries the burden of explaining inputs and result semantics. It does neither, leaving an agent unable to construct a correct call for this compatibility check.

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% and both parameters are opaque generic containers (params / params_json). The description says 'two specified CI actions' but gives no hint about how to supply them, so it fails to compensate for the undocumented 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?

States a concrete verb and resource: it determines whether two specified CI actions are compatible. That is clearly distinct from siblings like get_ci_lifecycle_active_actions or extend_ci_lifecycle_lease, though it does not differentiate itself from the closely related check_ci_lifecycle_not_allowed_action and check_ci_lifecycle_not_allowed_ops_transition.

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?

There is no guidance on when to run this check versus the other check_ci_lifecycle_* siblings, no prerequisites, and no mention of what scenario triggers a compatibility evaluation. The agent is left to infer usage from the name alone.

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