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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the bounded-page behavior, user scoping, and the Markdown return format, which go beyond annotations. It does not describe ordering or default page size, but that is a minor gap given the safety 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?

Two sentences with no redundant wording; the action, scope, and return format are all present. It is appropriately sized and front-loaded.

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?

The description, annotations, and schema together cover safety, pagination, and return structure. A minor omission is explicit guidance on paginating with cursor, but the schema's cursor description and the phrase 'bounded page' make it sufficient.

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 schema documents cursor but not limit; the description's 'bounded page' weakly implies limit controls page size. It does not explain defaults or how to use cursor for subsequent pages, so it only partially compensates for the 50% 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?

The description uses a specific verb ('List') and resource ('Tutorializer projects'), and scopes the operation to the authenticated user's accessible projects and a bounded page. This clearly distinguishes it from sibling tools like list_speeches, list_tutorials, and get_project.

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 clearly implies use when an agent needs a page of projects, but it does not explicitly name alternatives or exclusions. Sibling tool names suggest different resources, but no direct when-to-use vs alternative guidance is provided.

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