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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful nuance: claimed plans retain recovery references and submitted tasks are not canceled. However, it does not mention side effects, reversibility, or what happens to associated resources after denial.

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?

Two sentences, no filler, with the core action front-loaded and the important caveat placed second. Every sentence earns its place and the length is appropriate for a one-parameter tool.

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?

The tool is simple and the description covers the basic action and a key behavioral caveat. However, with no annotations, no output schema, and no parameter explanation, an agent may still be unsure how to obtain or populate confirm_token or what a successful denial returns.

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 0% for the only parameter, confirm_token, and the description does not mention it at all. The agent receives no guidance on where the token comes from, its format, or its role in the denial flow, so the description adds no meaning beyond the schema's title.

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 opens with the specific verb 'Deny' and the resource 'an unclaimed TikTok recreation,' making the action unmistakable. The second sentence clarifies what this tool does not do, distinguishing it from cancellation tools like campaigns_recreate_confirm or tasks_cancel.

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 clearly scopes use to unclaimed recreations and explicitly states this is not a task-cancellation tool, which provides useful exclusion criteria. However, it does not name an alternative tool or explicitly state 'use this when you want to reject an unclaimed recreation,' leaving some inference to the agent.

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