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

Annotations declare a non-readOnly, non-destructive, non-idempotent, open-world mutation. The description adds genuine behavioral context beyond this: the run must be in 'waiting' status for the call to work, which is a critical state precondition not expressed in the annotations.

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 tight sentences with the core purpose front-loaded, followed by the parameter-selection rule and the state precondition. No wasted 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?

For a mutation tool with no output schema, the description covers the two request modes and the waiting-status precondition. It doesn't state what happens after responding (e.g., run resumption) or error behavior if the precondition is unmet, but it is largely complete for correct invocation.

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% and the schema descriptions already explain approved ('true to approve, false to deny') and answers ('map of question text to answer'). The description's parameter guidance largely restates this, so the baseline 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?

States a specific verb and resource ('Respond to a human-in-the-loop request'), which is far more distinctive than most siblings like answerPulseDashboardQuestion or postRunMessage. It's clear what the tool does, though it doesn't explicitly distinguish itself from sibling response/message 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?

Gives explicit conditional guidance: use 'approved' for approval-type requests, 'answers' for question-type requests, and notes the 'waiting' status precondition. It doesn't name an alternative tool to use when the run is not waiting, but the selection logic between request types is well covered.

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