Phone Unsay

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

With no annotations, the description must carry the behavioral burden. It implies removal from page/history/pinned line and discloses a privacy guard around personal terms, but it does not state whether removal is reversible, what permissions are needed, or what happens when nothing matches.

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 purpose is front-loaded, and the parameter syntax is efficient. However, the second sentence is dense and contains a convoluted parenthetical about private terms files and git email, reducing readability.

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 annotations and no schema parameter descriptions, the definition covers purpose, selector syntax, and a privacy warning. It still omits important behavioral details: reversibility, permission requirements, no-match behavior, and exact scope of removal across page/history/pinned line.

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%, so the description must explain all parameters. It does so well: match accepts text with '|' and ignores case, since uses HH:MM for today, and n selects the last n captions. It does not clarify optional defaults or whether selectors can be combined.

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 clearly states a specific action and target: taking captions back off the phone page, its history, and its pinned line. It does not explicitly contrast with siblings such as phone_say or undo, so it falls short of full sibling differentiation.

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 explains selector options for match, since, and n, but gives no guidance on when to use this tool versus alternatives like phone_say or undo. There are also no exclusions or prerequisites for safe use.

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