tokportal_publish_bundle_video

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

The description explicitly states conditions (active TokPortal Coverage or permanent grandfathering, auto-renewal behavior) and the consequence of failure ('If Coverage cannot renew, no task or media mutation starts'). Annotations already mark readOnlyHint=false, so mutation is implied; the description adds valuable detail on when the mutation actually executes.

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 long, front-loads the core action, and every sentence adds meaningful information. No unnecessary words or redundancy.

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 covers the core behavioral contract (coverage/renewal conditions) but lacks any mention of return values or error handling. Since there is no output schema, the description could help by describing typical responses. The optional idempotency_key parameter is also not addressed. Still, it is adequate for a simple publish action.

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%, and each parameter already has a clear schema-level description. The tool description adds no additional parameter-specific meaning beyond the schema, so a 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 opens with 'Publish one video slot,' which is a specific verb+resource combination. The title in annotations confirms 'Publish one video slot.' This clearly distinguishes it from sibling tools like tokportal_publish_bundle (publishes entire bundle) and tokportal_publish_all_bundle_videos (publishes all slots).

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 does not provide any guidance on when to use this tool versus alternatives (e.g., tokportal_publish_all_bundle_videos for bulk publishing, or tokportal_publish_bundle for the whole bundle). It focuses on internal conditions (Coverage, auto-renewal) but offers no usage context or prerequisites for choosing this tool.

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