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

Without annotations, the description carries the full burden. It discloses that playback requires the password during protection and that Viddler swaps to a Mux signed-playback id, which is important behavioral context. However, it does not mention potential side effects (e.g., overwriting existing passwords) or permission requirements.

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 two sentences long, front-loaded with the core purpose, and every sentence adds value. No redundant or unnecessary information.

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 tool with only two simple parameters and no output schema, the description explains the behavior and return value (updated protection state). It lacks information on prerequisites (e.g., video existence, user permissions) and error conditions, but overall it covers the main functionality well.

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 schema already documents both parameters. The description adds that the password is a 'secret' viewers must enter, which provides minimal additional meaning. The baseline of 3 is appropriate since the schema already covers the parameter details adequately.

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 uses the verb 'gate' and specifies the resource 'a video behind a secret password', clearly indicating the action. It distinguishes from sibling tools like viddler_access_remove_password (remove password) and viddler_access_set_custom_url (custom URL) by focusing on password protection.

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 (when needing password protection) but does not explicitly state when not to use or mention alternatives like remove_password or set_custom_url. The context from sibling tools suggests differentiation, but the description itself lacks explicit guidance.

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