tv_pine_backup

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

Adds non-destructive nature, which matches destructiveHint=false. Annotations already provide readOnlyHint=true (though backup creates a file, it's debatable). Description provides minimal extra behavior beyond annotations.

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?

Single sentence, no unnecessary words. Front-loaded with key information: action, source, destination, and non-destructive property.

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?

Given one optional param, no output schema, and annotations present, description covers core purpose adequately. Could add detail on backup naming or overwrite behavior but sufficient for simple tool.

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%, baseline score 3. Description does not add additional meaning beyond what schema provides for the optional 'label' parameter.

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?

Clearly states verb 'Back up', resource 'current Pine editor source', and destination './backups with a timestamp'. Distinguishes from siblings like tv_pine_restore 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?

No explicit when-to-use or when-not-to-use guidance. Does not mention alternatives or context for use. Only states the action and non-destructive nature.

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