VidLens

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

Annotations are absent, so description carries full burden. '[~instant]' hints at timing, but missing critical behavioral details: return value (no output schema), irreversibility warning for a destructive operation, and explanation of deleteFiles parameter's disk impact.

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?

Three concise statements with no redundancy. Front-loaded with purpose. '[~instant]' tag is slightly cryptic but serves a behavioral purpose; otherwise efficient structure.

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?

Adequate for basic invocation but gaps remain: missing return value description (critical given no output schema), no safety warning for destructive operation, and no explanation of parameter validation rules despite 0 required fields in schema.

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%, establishing baseline 3. Description adds value by clarifying the 'one or the other' relationship between assetId and videoIdOrUrl, but completely omits deleteFiles parameter semantics.

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 clear verb ('Remove') and resource ('stored media assets'), distinguishing from siblings like removeCollection and removeCommentCollection. However, lacks explicit clarification of what constitutes a 'media asset' versus other removable resources on this server.

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?

Provides parameter-level guidance ('Specify assetId... or videoIdOrUrl') implying mutual exclusivity, but fails to specify that one parameter is required (schema shows 0 required). No tool-level comparison with alternatives like removeCollection or prerequisites mentioned.

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