obsbot_tail2_capture_photo

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

With no annotations, the description carries the full behavioral burden and delivers real value: it explains that the ack means the camera only *accepted* the trigger (not that the photo exists) and that the file lands on the card asynchronously. It omits permissions, rate limits, or timeout behavior, but the ack semantics are a meaningful disclosure beyond structured data.

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?

Three tight sentences, front-loaded with the primary action, then precondition, then result semantics. No filler, though the parenthetical endpoint note is slightly dispensable.

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?

Covers purpose, storage precondition, and async result semantics, and there is no output schema to compensate for. But it leaves the 'camera' parameter undefined and does not differentiate from snapshot siblings, so it is adequate rather than complete.

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?

There is one parameter ('camera') with 0% schema description coverage, and the description never mentions it, so it adds no semantic meaning. Since a lone, unnamed 'camera' string may still be inferable, this is above the floor but well short of compensating for the coverage gap.

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 and resource ('Trigger a still-photo capture on the Tail 2') and even names the underlying endpoint (POST capture/trigger), so the action is unambiguous. However, it never distinguishes this from siblings such as obsbot_tail2_snapshot or obsbot_capture_snapshot, leaving the agent to guess which photo tool applies.

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 a genuine precondition ('Needs storage (SD card — check obsbot_tail2_status's sdcard field)') that steers the agent to verify storage first. But it offers no when-to-use vs. alternatives guidance against the numerous snapshot siblings, so the routing decision remains implied.

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