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

Annotations only flag it as a non-read-only, non-idempotent, non-destructive write. The description adds real behavioral context beyond that: the post captures a snapshot at creation time ('the post keeps the snapshot taken now, so a later change needs a new post') and explains what forkers actually receive (media inputs default to empty). This materially affects the agent's publishing decision.

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?

Front-loaded with purpose, then prerequisites, then fork behavior. It is somewhat long (several sentences on include_in_fork), but each part is substantive and ties back to making the post usable. Slightly over-extended on fork mechanics that overlap adjacent tools.

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?

There is no output schema, and the description does not state what is returned (e.g., the new post ID). Otherwise it is strong: purpose, prerequisites, thumbnail constraints, and snapshot/fork implications are all covered. A brief mention of the return value would make it complete.

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 five parameters are already documented in the schema, including tags limits, thumbnail host constraints, and source_flow_id sourcing. The description restates source_flow_id sourcing ('from list_flows') that the schema already provides, adding little new parameter-level meaning. Baseline 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: 'Publish one of your flows to the cnaps.ai community. Creates a community post with a snapshot of the flow.' It also distinguishes the outcome ('others can then discover and fork your flow'), making it clearly separable from siblings like fork_community_flow or search_community.

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?

Gives concrete prerequisites ('Requires a source_flow_id (from list_flows) and a title') and context for using include_in_fork before publishing. It does not explicitly name alternatives or when-not-to-use cases, but the trigger condition for calling this tool is clear.

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