Apply drift remediation

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

Annotations mark destructiveHint=true, and description confirms mutating actions (file_bugs creates bugs, reopen moves tickets, relabel adds labels). Adds preview capability via dryRun and notes logging behavior. No contradictions.

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?

Two concise sentences front-loading key information: actions, verdicts, dryRun, and logging. No redundant words.

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?

Covers primary functionality but lacks details on return value or what exactly is recorded. No output schema, so description should hint at response shape. Adequate for a 5-param tool but leaves some gaps.

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 coverage is 40%, and description adds meaning to action (enumerated behavior) and verdicts (bands). Does not elaborate on runId or project params beyond schema. DryRun behavior is clarified.

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?

Describes specific verb 'remediate' on flagged tickets, with three enumerated actions and verdict bands. Distinguishes itself from sibling drift tools (drift_record, drift_report, drift_start) by focusing on remediation actions.

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?

Describes each action and dryRun preview, but lacks explicit guidance on when to use each action or when not to use the tool. No mention of alternatives or prerequisites.

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