metashunt_burst

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

With no annotations provided, the description bears the full burden of disclosing side effects. It states the tool returns samples and is decimated, but does not mention whether it is read-only, any permissions required, or potential side effects on the device.

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 well-structured, with clear bullet-like formatting for parameters. It wastes no words, though it could be more compact by merging related explanations.

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 the absence of an output schema and annotations, the description should cover the tool's overall behavior, return format, and parameter details. It covers the return count and rate but omits explanations for four of six parameters and does not describe the output structure or possible errors.

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 description explains 'trigger' and 'level' but does not clarify the meanings of 'rate_hz', 'max_points', 'threshold_pct', or 'abs_min_threshold_ma'. Since the schema provides no parameter descriptions (0% coverage), this is a significant 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?

The description clearly states the tool's purpose with a specific verb ('perform') and resource ('high-rate device burst read'). It distinguishes itself from sibling tools like metashunt_status and metashunt_start_capture by focusing on burst reads.

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?

No explicit guidance is given on when to use this tool versus alternatives. The description mentions 'high-rate' and 'burst', but does not clearly differentiate from other read/stream tools or indicate preferred use cases.

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