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

Annotations already declare a safe, closed-world read, so the bar is lower; the description still adds real context the agent would not otherwise have: the result ordering ('latest edited first'), the exact per-row payload (id, name, kind, first line, Studio link), and the pagination contract. It does not mention the default page size of 20 or the 100-item cap.

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, front-loaded with the resource and sort order, then return shape, then filtering and paging. There is minor looseness in 'made in the Lazybird Studio or here', but no sentence is filler.

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?

With no output schema, the description usefully enumerates the returned fields and the sort order, which is exactly what an agent needs to decide whether to call it. The gap is the undocumented limit parameter (default 20 / max 100), which is missing from both schema and description.

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 67%: q and cursor are already documented in the schema, and the description largely restates them. Its one addition is clarifying that the cursor is the 'returned' next-page value tying requests to responses. The limit parameter has no description in the schema and is not addressed in the description either.

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 states the resource (the user's Lazybird projects, audio or video) and the ordering (latest edited first), plus what each row contains, so an agent can tell it is a summary listing rather than a single-record read like read_project. It never uses an explicit verb and does not name a sibling, so differentiation is inferred rather than stated.

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?

It gives operative guidance on filtering ('filter by words in the name') and pagination ('pass the returned next-page cursor'), which tells the agent how to narrow and page. It offers no when-to-use versus when-not-to-use framing and never points to read_project or edit_project for follow-up, leaving alternative selection to inference.

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