Review With Agent

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

The description adds a small behavioral note about queueing and a support condition, but does not elaborate on side effects (e.g., destructive behavior) or delivery mechanics. Annotations already declare destructiveHint: true and readOnlyHint: false, so the description contributes limited extra context beyond what is already structured.

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 a single, front-loaded sentence with no fluff. It clearly states the action and a condition, achieving excellent conciseness and structure.

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 tool with nine parameters, nested objects, and an output schema, this one-line description is severely under-specified. It provides no guidance on constructing the workspace, configuring the review, or interpreting the output, making correct invocation highly unlikely.

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?

The description does not explain any of the nine parameters. It alludes to 'target and delivery' but provides no semantics for them. With schema description coverage at only 22%, this is a significant gap that the description fails to compensate for.

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 ('Queue a typed review') and a condition ('when the session backend supports its target and delivery'), clearly identifying the tool's core purpose without being a tautology. However, it does not explicitly differentiate from sibling tools like agent_session_review, so it falls short of a 5.

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 a conditional prerequisite regarding session backend support, which hints at when the tool is appropriate. But it does not name alternatives or specify when to use this tool instead of batch_prompt or agent_session_review, leaving usage guidance only partially developed.

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