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

The description adds substantial behavior beyond the annotations: it saves a draft but never posts, generates one AI reply per team call, takes about 10–15 seconds, and defines what setup_required and syncing mean for the user. This is exactly the kind of operational and side-effect detail an agent needs before invoking the tool.

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 purpose and safety guarantee are front-loaded, followed by latency, an example, and actionable error-state handling. Every sentence earns its place and no context is buried.

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 complexity, the annotations, and the output schema, the description covers what the tool does, its non-posting safety profile, expected latency, and error-state behavior. An agent has enough to call it correctly without needing more.

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 100%, so the input schema already documents tone, review_id, and instructions. The description's example mirrors those same fields without adding syntax or semantics beyond the schema, so the baseline of 3 is appropriate.

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 verb and resource: 'Generates an AI reply draft for one review and saves it as a draft.' It distinguishes the write-as-draft behavior from posting ('Never posts it'), but it does not explicitly name or contrast the sibling create_reply_draft tool.

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?

It gives clear operational context: use this for one review, save as a draft, and a person sends it later in the app. It also explains the setup_required and syncing states, though it does not explicitly say when to choose this over create_reply_draft or other reply tools.

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