tokportal_publish_all_bundle_videos

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

Annotations provide no behavioral hints beyond type, so the description carries the burden. It discloses key behaviors: preconditions (coverage/grandfathering), side effects (automatic renewal at stored rate), and failure mode (no mutation if renewal fails). This adds substantial value beyond the minimal annotation set.

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?

Three sentences with no wasted words. The first sentence immediately conveys the purpose, followed by essential conditions. Each sentence earns its place.

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 main precondition and failure scenario, which is critical for a mutation tool. It does not describe return values (no output schema), but that is not required. It could mention what happens on success more explicitly, but the intent is clear.

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 baseline is 3. The description does not elaborate on parameters (id, idempotency_key); the schema already documents them adequately. No additional meaning or usage guidance for parameters is provided.

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 clearly states 'Publish all configured videos on an active bundle,' providing a specific verb and resource. It distinguishes from siblings like tokportal_publish_bundle (publishes the bundle itself) and tokportal_publish_bundle_video (single video), making the scope unambiguous.

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 implies when to use by specifying 'active bundle' and explaining prerequisites (coverage/grandfathering, renewal conditions). While it does not explicitly compare to alternatives, the context is sufficient for an agent to understand when this tool is appropriate.

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