VNyan Spout2 cameras

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

No annotations exist, so description carries full burden. It discloses that the tool accesses a plugin, is live and read+write, and that removal is not safe. However, does not mention return values or idempotency of addCamera.

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?

Two concise sentences. First sentence covers purpose, second adds critical usage warning. No fluff, front-loaded.

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?

Description covers purpose and a key warning, but lacks return value information (e.g., what list returns, success for add). With no output schema, this gap reduces completeness. Parameter details are well-covered 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%, so baseline is 3. Description adds minimal value beyond schema, mostly repeating names. The only extra insight is that flag1-4 have unknown meanings. Could clarify ignored params when linkToMainCamera is true, but schema handles that.

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 clearly states the tool lists or adds Spout2 cameras, with a specific verb and resource. It distinguishes from sibling tools by explicitly mentioning Spout2 cameras, which none of the other tools cover.

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 explicit warning about lack of safe removal and directs users to VNyan's own panel for that action. Also mentions source and read/write nature. Lacks explicit when-to-use vs. alternatives beyond the removal guidance.

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