Preview supervision drafts

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

The description discloses that no records are created, the tool returns a short-lived preview token, and user review is required. This aligns with annotations (readOnlyHint=true, destructiveHint=false) and adds useful behavioral context beyond what annotations provide.

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 extremely concise, consisting of two sentences with no redundant information. Every sentence adds value by stating the core function, the absence of record creation, the return value, and the user requirement.

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?

Given the tool's moderate complexity (5 parameters, no output schema), the description covers the essential aspects: purpose, non-destructive nature, return value, and user action. It lacks mention of error conditions or parameter interdependencies but is sufficient for a preview tool.

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?

With 60% schema description coverage, the description does not add extra parameter-level guidance. It only says 'Open and populate', which does not clarify the meaning or format of parameters like topic or students beyond what the schema 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 clearly states the tool opens and populates a preview page without creating records, and returns a short-lived preview token. This distinguishes it from siblings like camcors_create_supervision_drafts, which likely create records directly.

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 specifies that the user must review the visible page before any drafts are created, providing clear context for when to use this tool. However, it does not explicitly state when not to use it or mention alternatives for direct draft creation.

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