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

Annotations already cover readOnly/openWorld/non-destructive, so the safety profile is free. The description adds value the annotations do not: it spells out the returned fields and clarifies that the caption is OpusClip's description plus hashtags, which affects how an import will look. It does not mention pagination or result limits, which keeps it short of a 5.

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, deprecation notice front-loaded so it is the first thing read. Every clause carries information: replacement target, return fields, caption composition, and ID provenance.

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?

There is no output schema, and the description compensates by listing the returned fields and explaining the caption's composition. For a deprecated read tool with full schema coverage, that is close to complete; only result volume/pagination behavior is unaddressed.

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 coverage is 100% and both parameter descriptions already say 'from list_opusclip_projects'. The description restates this sourcing hint, adding only slight reinforcement rather than new meaning, so the baseline 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?

States a specific verb and resource with scope: 'Lists the clips OpusClip made in one project', and enumerates the returned fields. It also names the replacement tool and the downstream tool (import_opusclip_clips), so an agent can place it precisely among the sibling list_* and import_* tools.

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 tells the agent not to use it ('Deprecated: use list_import_items with source opusclip') and names the exact alternative plus the argument variant. It also explains prerequisites: get project_id and org_id from list_opusclip_projects.

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