VidLens

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

Adds important context that the operation is 'local' and deletes both the collection and its 'search index', indicating cascading effects. '[~instant]' suggests synchronous execution. However, lacks critical safety disclosure about irreversibility given the destructive nature and absence of 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?

Extremely concise with core action front-loaded. '[~instant]' tag is slightly cryptic but efficiently conveys performance characteristic. No redundant text.

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 a single-parameter deletion tool, identifying scope (local collection + index). However, given 0% schema coverage and no annotations, it lacks necessary safety warnings about data destruction that would typically be required for irreversible operations.

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 has 0% description coverage. The description fails to compensate by explaining the collectionId parameter, though the parameter name is intuitive given the tool name.

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?

Clear verb 'Delete' and specific resource 'local comment collection and its search index'. Distinguishes from generic removeCollection by specifying 'comment' and 'local', though could better differentiate from clearActiveCommentCollection.

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 versus clearActiveCommentCollection (which clears the active collection) or removeCollection. No prerequisites 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.