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

Annotations are minimal (all false), so the description carries the burden. It adds useful context: the destination library ('Lands in the same Playbooks library the web app lists, runs and manages') and that it is 'Free' (no credit cost). However, it does not clarify whether saving with an existing name overwrites, creates a new entry, or if it is idempotent. This is a notable gap for a write operation.

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 description is four sentences long but each sentence earns its place: it defines the resource, gives usage scenarios, states the destination, and draws contrasts with alternatives. It is slightly longer than necessary but well-organized and front-loaded with the core purpose.

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 7-parameter write tool with no output schema, the description covers the essential context: what a playbook is, when to use it, where it lands, whether it costs credits, and how it differs from related tools. The only missing piece is whether it creates a new entry each time or updates an existing one, which an agent would need to know for correct invocation.

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 100%, so all 7 parameters already have descriptions. The tool description broadly refers to 'hooks, angles, formats, concrete plays' which mirrors the schema, but adds no new syntax or format details beyond what the schema provides. It stays at the baseline of 3 without further elaboration.

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 specific verb ('Save') and a specific resource ('reusable PLAYBOOK') and defines what a playbook is with concrete components (hooks, angles, formats, plays). It explicitly distinguishes itself from save_skill and the swipefile, making its purpose unmistakable even among many siblings.

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 gives clear when-to-use guidance: 'Use it to keep what a competitor_teardown or mine_angles just found, or to bank a creative you want to repeat.' It also states what it is not for by naming save_skill and the swipefile as alternatives, leaving no ambiguity about choosing this tool.

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