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

Beyond the sparse annotations, the description discloses that this creates a public post, returns a postId and public postUrl, and can attach media via imageUrls or reference an AIGE generation via fromHistoryId. It still omits meaningful behavioral details such as retry/idempotency behavior despite the idempotencyKey parameter and idempotentHint=false annotation.

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 compact and front-loaded: purpose first, attachment modes second, usage cues third, return values fourth, and a short note on tags. Every sentence contributes actionable information without repetition.

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 publish tool with no output schema, the description helpfully covers the core action, primary media-attachment paths, and return values. It is not fully complete for a seven-parameter mutation because idempotency, fromTaskId, and videoUrls are not explained, but the main calling context is present.

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 0%, so the description must carry parameter meaning. It explains imageUrls, fromHistoryId, and optional tags, but leaves text, videoUrls, fromTaskId, and especially idempotencyKey unexplained, leaving several caller decisions to inference.

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: publishing a post to the AIGORA social feed at aigora.ws. It clearly frames the action as sharing/publishing a creation to a feed, which separates it from generation-oriented siblings such as antix_generate_image or antix_compose_social_post.

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 concrete when-to-use cases: sharing a creation, publishing to a feed, posting to social, or showing work to the community. It does not explicitly name alternatives or when-not-to-use cases, such as composing content versus publishing an approved/scheduled post, so it falls 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.