VidLens

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

With no annotations provided, the description carries the full disclosure burden. It successfully indicates cascade behavior ('and its search index') and performance characteristics ('[~instant]'). However, it lacks information on reversibility, required permissions, or error conditions.

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?

Extremely concise at two phrases. The core action is front-loaded. The '[~instant]' notation is compact if slightly cryptic. Only deduction is that brevity comes at the cost of parameter documentation.

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 single-parameter deletion tool without output schema, the description covers the primary effect adequately. However, the complete lack of parameter documentation (given 0% schema coverage) leaves a significant gap for agent operation.

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% and the description fails to compensate by explaining the 'collectionId' parameter—what format it takes, where to obtain it (likely from 'listCollections'), or any constraints. The description mentions 'collection' generally but not the specific parameter.

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 uses a specific verb ('Delete') and clearly identifies the resource ('local transcript collection and its search index'). It effectively distinguishes from siblings like 'removeCommentCollection' (comments vs transcripts) and 'clearActiveCollection' (state clearing vs deletion).

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?

No explicit guidance on when to use this tool versus alternatives like 'clearActiveCollection' or 'removeCommentCollection'. No prerequisites mentioned (e.g., whether collection must be inactive first) or warnings about data loss.

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