obsbot_tail2_export_log

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

With no annotations, the description carries the full burden and largely meets it: it discloses output size (~12 MB tar.gz), exact contents (ust.json settings tree, runtime status snapshot, factory records, kernel logs), and server-side latency (~10-20 s). It stops short of stating auth/permission needs or failure behavior.

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?

A single dense sentence plus one follow-up, front-loaded with the action, endpoint, and destructive-free save semantics. Every clause (size, contents, duration) adds actionable information; no filler.

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?

No output schema and no annotations, so the description does its own heavy lifting on return artifact, contents, and timing. It omits what `path` points to (file vs directory), error/failure behavior, and the `camera` param, leaving small but real gaps.

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%, so the description must compensate. It clarifies `path` as the save destination for the downloaded archive, but says nothing about the optional `camera` parameter (presumably a device selector), leaving one of two params semantically dark.

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 a specific verb (download/save) and resource (full diagnostic bundle / log archive), names the underlying endpoint GET /camera/test/log, and equates it to OBSBOT Center's Export Log button. No sibling tool produces a log bundle, so the agent can place it unambiguously.

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?

Usage is implied by the diagnostic-bundle framing (use this when troubleshooting), but there is no explicit when-to-use/when-not statement and no alternative tool is named or excluded. Adequate but leaves the agent to infer the trigger condition.

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