publish_drafts

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

With no annotations provided, the description carries the full burden. It discloses the main behavioral effect (draft comments becoming visible to other reviewers in one batch), which is helpful. However, it omits details like the irreversibility of the action, permission requirements, or what happens to the draft records afterward, so it is adequate but not rich.

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 two sentences, front-loaded with the action, and every sentence contributes value. It is concise with no filler, and the analogy to the Gerrit UI is a compact way to convey behavior.

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?

The tool is a simple mutation but has four parameters and no output schema or annotations. The description covers the core action but omits parameter semantics and edge cases. It is minimally adequate for an agent to understand the main purpose, but not complete for correct invocation with all parameters.

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 compensate by explaining the parameters, but it mentions none. The schema itself only provides titles and defaults, not meanings. The labels and message parameters are completely unexplained, leaving the agent without guidance on how to use them.

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 states a specific action ('Publishes all pending draft comments on a CL as a single review') with a clear resource and outcome. It also distinguishes from sibling tools by emphasizing the batch nature ('in one batch') and the Gerrit 'Send' equivalence, making it unmistakable.

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 gives clear context for use: when you have pending draft comments and want to send them as a review. The analogy to clicking 'Send' in Gerrit provides practical guidance, but it does not explicitly name alternatives or exclusions, such as when to use post_draft_comment or post_review_comment instead.

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