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

The description is consistent with the readOnlyHint annotation and adds minimal context beyond it, specifying the scope 'configured for a quiz.' It does not disclose pagination, ordering, return format, or edge-case behavior. Since annotations already cover the read-only nature, the description adds limited behavioral insight.

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 a single, front-loaded sentence that immediately conveys the action and resource. It is appropriately concise with no unnecessary 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?

For a simple read-only list tool with one documented parameter and a readOnlyHint annotation, the description is mostly adequate. However, without an output schema, it does not describe the response structure, which could leave the agent uncertain about what is returned. Given the tool's simplicity, the description is nearly complete but lacks explicit mention of the return list format.

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?

The tool description does not add information about the quizId parameter beyond the schema, which already provides a detailed description (YouTube-style 11-character base64url). Schema description coverage is 100%, so the baseline of 3 applies.

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 specific verb 'List' and identifies the resource as 'video hooks configured for a quiz,' clearly distinguishing it from sibling tools for creating, updating, or deleting hooks and from listing other resources like quizzes or questions.

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 usage for viewing hooks of a specific quiz, but provides no explicit guidance on when to use this tool versus alternatives such as creating, updating, or deleting hooks. No exclusions or alternative tools are mentioned.

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