VidLens

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

No annotations provided, so description carries full burden. Adds '[~instant]' performance hint and discloses stateful side effect (modifies searchComments behavior). Omits persistence scope (session vs permanent), validation behavior, and error handling details.

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?

Single efficient sentence front-loaded with the action. '[~instant]' tag adds behavioral metadata without verbosity. Zero redundancy.

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?

Appropriate for a simple one-parameter state configuration tool. Core purpose and sibling relationship are clear. Parameter documentation gap and lack of output/error specification prevent higher score given 0% schema coverage.

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% with one undocumented parameter. Description mentions 'comment collection' generally but fails to describe the collectionId parameter format, valid values, or constraints (e.g., must be from listCommentCollections). Insufficient compensation for schema gaps.

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 action 'Set', specific resource 'default comment collection', and explicit scope 'when collectionId is omitted'. Distinguishes from sibling setActiveCollection by specifying 'comment' and from clearActiveCommentCollection by describing the positive configuration action.

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?

Explicitly identifies sibling tool searchComments as the consumer of this setting and describes the specific condition triggering its use (omitted collectionId). Lacks explicit 'when not to use' guidance or prerequisite warnings.

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