tv_pine_restore

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

Goes beyond the annotations by explicitly stating 'DESTRUCTIVE: overwrites editor contents (does not auto-save),' adding crucial behavioral context about what is overwritten and the lack of auto-save.

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 efficiently convey the action, default behavior, and destructive warning. No wasted words.

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 simple restore tool with no output schema, the description covers the restoration process and destructive nature adequately. Minor omission: no mention of success/failure feedback, but it's not critical.

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 coverage is 100% and the schema describes backupName as 'Exact backup filename from tv_pine_list_backups.' The description adds value by explaining the default behavior when backupName is omitted.

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 'Restore a backup into the Pine editor' which is a specific verb-resource pair. It distinguishes from sibling tools like tv_pine_backup and tv_pine_list_backups.

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?

Provides guidance on omitting backupName to restore the most recent backup and warns about destructiveness. However, does not explicitly state when to use this tool over alternatives like tv_pine_create or tv_pine_patch.

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