metashunt_start_capture

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

No annotations are provided, and the description does not disclose potential side effects such as whether an existing session is overwritten, whether it creates a new session if none exists, or if any data is lost. The background capture behavior is mentioned, but other behavioral aspects are omitted.

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?

The description is concise and to the point, containing only essential information about starting capture, the return value, and the stopping condition. It avoids unnecessary detail and is well-structured for quick understanding.

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?

Given that this tool is part of a suite with related tools (burst, stream_now, set_trigger, etc.), the description does not explain when to use this instead of others, nor does it clarify how the capture works in relation to session management. It is minimally sufficient for a single tool but lacks broader context.

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?

The schema has zero parameter descriptions, and the tool description does not explain what 'meta', 'label', or 'session' mean or how they affect the capture. The phrase 'named session' hints that 'label' or 'session' might be the name, but it's not explicit.

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's function: starting continuous capture into a named session, and it explicitly mentions the return value (session name). The verb 'Begin' and the object 'continuous capture' make the primary purpose unambiguous.

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?

The description indicates that sampling continues in the background until metashunt_stop_capture is called, which gives a clear usage condition (use this for ongoing capture, and use stop_capture to end it). However, it doesn't explicitly differentiate from siblings like burst or stream_now, so it's slightly incomplete but still useful.

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