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

The description discloses experimental status, the narrow 'reliable output' scope, missing structured caption/scheduler fields, and the 3 MESH/call cost. This adds meaningful behavioral context beyond the sparse annotations and does not contradict them.

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 tight and front-loaded: purpose, input, reliable output, limitation, and cost each get a short clause or sentence. There is no redundant or filler content.

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?

The description gives enough high-level context to select the tool, but not enough to construct the actual 'input' payload: it never shows a concrete example or field names for the clip library/reactions. With no output schema and one generic required object, this is a genuine gap.

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?

While the schema already describes the input generically as a 'capability-specific payload', the description adds the key semantic guidance that the payload should contain a clip library plus the last post's reactions. It lacks a concrete example or field names for this specific tool, so it does not earn a 5.

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?

It clearly identifies the tool as an 'experimental content-ranking planner for repost loops' and states the reliable output: a next-pick recommendation and an explanatory note. However, it does not explicitly differentiate it from sibling tools such as lane-post or mesh_publish, leaving some ambiguity about when this one is preferred.

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 usage context: feed it a clip library and the last post's reactions, and expect a recommendation/note. It does not, however, state when not to use it or which sibling alternative to choose, so it stops short of full routing guidance.

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