Publish or unpublish a creation

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true), the description discloses the required scope ('needs the publish scope'), the public feed implication, and refusal conditions for certain creation types. This adds significant behavioral context without contradicting any annotations.

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 three sentences, front-loaded with the primary function, and every sentence contributes useful information. There is no redundancy 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 simple two-parameter tool with no output schema, the description covers the essential context: scope requirement, behavior, and usage constraints. It lacks explicit mention of success/error response formats, but given the simplicity and annotations, it is sufficiently 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 coverage is 100%, so the baseline is 3. The description adds meaning beyond the schema by explaining the effect of the 'publish' action and the conditions for unpublish, making the action parameter's semantics clearer. However, it does not add details about creationId format beyond what the schema already provides.

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 opens with 'Flip ONE creation's public visibility', a specific verb and resource that clearly indicates a toggle action. It further clarifies the exact effect by stating 'Publishing puts it on the 2DAI public feed', which distinguishes this from other creation management tools.

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 provides explicit usage guidance: 'Publish only when the user explicitly asked' sets a clear condition for publishing, and 'Unpublish always works on a public row' clarifies when unpublish is appropriate. It also notes platform refusals for raw uploads and NSFW-flagged creations, offering practical constraints.

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