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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds behavioral detail beyond that: it acts only on the explicit project_id (never the active pointer), returns the project identity with its result, and marks unused files as AVAILABLE. This enriches the agent's understanding of side effects and scope.

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 dense yet well-structured. It front-loads the critical scope constraint (PROJECT-SCOPED) and then proceeds logically: what is returned, kind meanings, and the notable unused-file behavior. No sentence is wasted; all information is actionable.

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 provides necessary context: it returns project identity and marks unused files as AVAILABLE, and it explains each kind. It doesn't describe the full asset record structure, but for a listing tool with simple parameters and read-only annotations, it gives sufficient detail for correct invocation and interpretation of results.

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 50%: project_id has a detailed description, but kind has none. The description compensates by explaining every valid value of kind ('music', 'clip', 'image', 'render', 'all') and their meaning, plus how to use the results. This adds significant semantic value beyond the schema.

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 explicitly states the tool lists all assets in a project, scoped to a specific project_id. It differentiates from siblings by explaining what each kind returns (music, clip, image, render, all) and how to use those results with specific tools (add_music, add_voiceover, insert_media). This is a precise, resource-specific purpose.

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 clearly states when to use this tool: for project-scoped asset listing including unused uploads. It gives explicit usage guidance by mapping each kind to its downstream consumer tool and notes that unused files are marked AVAILABLE so they can be placed without re-upload, which is a practical usage hint.

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