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

Annotations already declare this is not read-only, is open-world, and is destructive, and the description supports that by explaining that it checks for new posts and reposts them or fills scheduled slots. It adds useful behavioral context such as the returned counts, one-line summary, rate limits, and the requirement that the workflow be enabled.

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 front-loaded with the core action and uses each sentence to convey distinct useful information: immediate execution, behavior, returns, limits, and prerequisite. There is no repetition or filler.

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 destructive open-world mutation tool with no output schema, the description supplies the key operational context an agent needs: what it does, when it runs, rate limits, prerequisite state, and return shape. It could be more complete about permissions or failure behavior, but the essentials are covered.

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?

There is only one parameter, workflow_id, and the schema has 100% description coverage including where to get the ID. The description does not add parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 and resource: it runs a Repurposing workflow immediately rather than waiting for its automatic run. It also clarifies the two modes of action, checking for new posts and reposting them or filling scheduled slots, which distinguishes it from sibling management tools like update_repurposing_workflow.

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?

Usage is clearly implied: use this when an immediate run is needed instead of the next automatic 15-minute run. It also gives prerequisites and limits, including that the workflow must be on and the rate limits of once per minute or every 5 minutes, though it does not explicitly name alternatives or exclusions.

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