restack_note

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

With no annotations, the description fully covers behavior: it indicates a write operation (WRITE), explains the dry_run preview mechanism, and notes the limitation that the on parameter cannot reverse a restack. No contradictions with 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?

The description is concise (two sentences plus example and sibling reference) and front-loaded with the action. It efficiently packs essential info but could benefit from slight restructuring for 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?

Given no annotations, no output schema, and a simple tool with three params (0% schema coverage), the description provides complete context: purpose, parameters usage, limitations, and a sibling alternative. An agent has enough to use the tool correctly.

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?

The description adds meaning to key parameters: dry_run as preview and on as ineffective for false. It includes an example with note_id. While the schema has 0% description coverage, the description compensates well but could clarify note_id format more explicitly.

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 the tool's action ('restack a Note') and its effect ('broadcasting it to your subscribers' feeds'). It also distinguishes from the sibling tool 'restack_post' by specifying that this is for short-form Notes and that tool is for long-form posts.

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 provides explicit usage guidance: defaults to dry_run=true as a preview, must set dry_run=false to actually publish. It also warns that Substack does not support un-restacking (on=false is a no-op), which is critical for correct usage.

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