react_to_post

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

No annotations provided, so description carries full burden. It discloses default values (reaction=❤, on=true, dry_run=true), the behavior of 'on' parameter (true=add, false=remove), and the dedup/idempotency behavior. Missing explanation of error handling or side effects, but covers key behavioral aspects.

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?

Three sentences, no fluff. Starts with 'WRITE' to indicate operation type. Every sentence adds value: defaults, sibling alternative, behavioral nuance.

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 toggle tool, description covers core functionality, defaults, and cross-references sibling. Missing explanation of 'pub' parameter and output behavior (no output schema needed). Adequate for typical use.

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 has 0% description coverage, so description must add meaning. It explains 'reaction' defaults to ❤, 'on' controls add/remove, and 'dry_run' defaults true. However, 'pub' parameter is not explained at all, and 'dry_run' semantics are implied but not explicit (e.g., what does dry_run do?). Partial coverage.

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 'Add or remove a reaction on a post', specifying the resource (post) and action (add/remove reaction). It also distinguishes from the sibling tool 'react_to_comment'.

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?

Explicitly says when to use this tool (reacting to a post) and when to use the alternative (react_to_comment for comment-level reactions). Also notes that reactions are not deduped but Substack handles idempotency.

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