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

Annotations already carry readOnlyHint=false, idempotentHint=false, and destructiveHint=true, so the safety profile is known. The description adds valuable behavioral context beyond annotations: repeating the call creates another tutorial, and this action records a definition rather than rendering a video. No contradiction with annotations.

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 with no wasted words. It front-loads the core purpose, then packs the non-idempotency warning and the video distinction into compact, meaningful clauses. Every 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?

An output schema exists, all parameters are described in the input schema, and annotations cover the read-only/idempotency/destructive profile. The description supplies the missing behavioral nuance about duplicate creation and clarifies the tool is not for video rendering. Nothing material is missing for correct invocation.

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%, so the schema fully documents name, projectId, and defaultVoice. The description adds no parameter-specific detail, but it does reinforce the importance of the name through the duplicate warning. Baseline 3 is appropriate given the high schema coverage.

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 states a specific action and resource: 'Create a Tutorializer tutorial definition inside a project.' It also distinguishes itself from video creation by noting it records the tutorial but does not record or render a video, which clearly separates it from siblings like create_video and create_speech.

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 tells the agent to list tutorials and confirm the intended name first because repeated calls create duplicates. It also clarifies this tool does not record/render a video, providing a useful exclusion. It stops short of explicitly naming an alternative tool, but the guidance is clear and actionable.

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