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

Discloses traits well beyond the annotations: a 20-per-project-per-day cap, that it is FREE, that it is a MUTATION, and that it requires org admin rights. Annotations already mark it non-readonly, non-destructive, and idempotent, so the description's added caveats about limits, cost, and permissions are genuinely valuable.

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?

Three dense sentences that are front-loaded with the core effect before the cap, exception, and permission notes. Every clause carries information, though the embedded draft_patch value-argument clause makes it slightly dense rather than crisply scannable.

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?

For a 2-parameter mutation with no output schema, the description supplies everything needed: the behavioral change, the cap, cost, permission requirements, and the critical exception. Annotations cover the safety profile, so no essential context is missing.

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 100%, so both parameters are already documented, giving a baseline of 3. The description adds meaningful interpretation by clarifying that the rule applies only to freshly AI-drafted patches and never to hand-typed replacement values, which shapes how the issueType scope should be understood.

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 specific verb (enable) and resource (patch auto-publish) for a given issue type, and describes the exact behavioral change: AI-drafted patches publish immediately rather than waiting for a manual publish_patch call. This lets an agent distinguish it immediately from the sibling publish_patch and disable_patch_auto_publish tools.

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?

Clearly explains the operational context (replaces the manual publish_patch step, applies per issue type, requires org admin) and notes the key exception that hand-typed draft values are never auto-published. It does not explicitly point to disable_patch_auto_publish as the reversal path, leaving that inference to the sibling name.

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