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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so 'read only; it renders and deletes nothing' largely restates structured data; the only genuinely new behavioral fact is that the call is free. It does add pagination behavior (50 per page, cursor for the next page) and the per-item payload fields, which go beyond the 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?

Front-loaded with the use case and example utterances, then pagination mechanics, then an exclusions block. Every sentence carries information an agent needs; nothing is padding.

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 two-parameter read tool with full annotation coverage and an output schema, the description covers triggering intent, scope boundaries, pagination, and the returned fields. Nothing an agent needs in order to call it correctly or choose a sibling instead is missing.

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 0%, so the description carries the burden, and it does: it supplies the valid range for limit (1-50), the page size ceiling, and how to chain pages ('pass next_cursor as cursor'). The only gap is that the schema default of 20 and the cursor's empty-string default are never explained, leaving a small inconsistency with 'returns up to 50 per page'.

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 ('browse the Library') and immediately defines the resource as 'the rendered video files saved in their RipClip account', which is exactly the ambiguity an agent would otherwise have to guess at. It also names the sibling tools it is not (list_clips, list_projects, search), so the tool is distinguishable without opening any schema.

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?

Gives concrete user phrasings that should trigger it ('what's in my Library', 'list my exports') plus an explicit 'Not for:' clause routing to list_clips for clip-job output, list_projects for source videos, and search for title lookup. When-to-use, when-not-to-use, and alternatives are all present.

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