draft

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

No annotations are provided, so the description carries the full burden. It does not disclose that clearing a draft destroys content, whether the operation is scoped to the current session/chat, or whether any permissions are required. For a tool that can delete user content, this is a meaningful gap.

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?

It is a single, front-loaded sentence with no wasted words, but its extreme brevity is under-specification rather than effective conciseness. It does not earn its place as a complete definition.

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?

With no annotations, no output schema, and no parameters, the description is the only source of behavioral information, and it omits the mechanism for identifying the chat, the destructiveness of clearing, and any response behavior. It is insufficient for an agent to call this tool confidently.

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 schema declares zero parameters, which normally sets a baseline of 4, but the description never explains how the target chat or draft content is identified given that no inputs exist. That omission leaves a real semantic gap rather than merely repeating structured data.

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 verb and resource ('Save or clear a draft in a chat'), which is more than a restatement of the name, but it bundles two opposite operations (save vs. clear) without explaining how they are selected. It also fails to distinguish itself from the sibling 'drafts' tool, leaving the agent unsure which one to pick.

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?

There is no guidance on when to use this tool rather than 'drafts', 'edit', or 'delete', and no indication of the conditions under which a draft is saved versus cleared. Usage is only implied by the tool name.

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