Create supervision drafts

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

Description adds behavioral context beyond annotations: creation requires explicit user confirmation and does not submit. Annotations already indicate non-readonly, non-destructive, and open-world. No contradictions, but could mention potential side effects if confirm is not true (though schema enforces it).

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?

Two concise sentences, immediately clear what the tool does and when to use it. No wasted words.

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?

Description covers prerequisites (preview token), user action requirement (confirm), and boundaries (does not submit). With no output schema, could mention expected outcome (e.g., draft IDs returned), but overall sufficient for a creation 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?

Schema covers confirm with description, but previewToken lacks description. Description adds 'represented by a preview token' linking to previewToken parameter. Provides context beyond schema for previewToken, though format/pattern already exist. Schema coverage 50% is compensated by description.

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?

Description clearly states it creates supervision report drafts using a preview token after user confirmation. Distinguishes from sibling tools like camcors_prepare_supervision_drafts (which likely creates the preview) and camcors_submit_reports (which submits).

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?

Explicitly states 'Call only after the user has reviewed the visible preview and explicitly confirmed creation.' Also notes it does not submit drafts for approval or payment, guiding the agent on when and when not to use this tool.

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