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

With no annotations present, the description carries the behavioral disclosure burden. It clearly explains that the tool returns a short, ready-to-send continuation message that anchors to existing work, and it adds the API key requirement. It does not detail edge-case behavior or output formatting beyond this, but the core invocation-relevant behavior is transparent.

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 compact and front-loaded: the core purpose, usage boundary, return behavior, and access requirement each get one sentence with no filler. Every sentence earns its place and supports selection or invocation.

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 generative tool with no output schema, the description provides enough context to invoke it correctly: what it returns, when to use it, when not to use it, how it differs from improve_prompt, and that an API key must be appended to the connector URL. The schema covers the parameters, so the description does not need to repeat them.

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 parameters next_request, original_goal, and conversation_summary already carry clear meaning. The description adds overall context about follow-up generation and the tool not restarting work, but it does not add much per-parameter detail beyond what the schema already provides. 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?

The description states a specific verb and resource: it writes the user's next follow-up message for an in-progress conversation. It also distinguishes itself from sibling tools by saying it is not for brand-new tasks, and specifically names improve_prompt as the alternative.

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 explicit when-to-use and when-not-to-use guidance: use it to 'refine, deepen, or continue earlier work,' and avoid it for 'a brand-new task' where improve_prompt should be used instead. This clearly routes an agent to the correct sibling.

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