heuristic_enable_disable

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

No annotations are present, requiring the description to disclose behavioral traits. The description only states 'Analyze with selected heuristic dissectors', but does not explain what happens during analysis (e.g., whether it modifies state, requires prior capture loading, or has side effects). It fails to disclose destructive or read-only nature.

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 a single sentence, which is concise, but it is severely under-specified for a tool with four parameters and no schema descriptions. Every sentence should add value; here it does not earn its place due to lack of substance.

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?

Despite having an output schema that might document return values, the description is too brief given the tool's complexity (4 params) and the presence of many sibling tools. It does not explain core functionality like how enable/disable lists interact, what 'limit' controls, or the overall analysis process, making it incomplete for reliable agent use.

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?

With 100% parameter schema coverage missing (0%), the description must compensate but adds no information about the four parameters (capture_path, enable, disable, limit). The description does not explain their semantics, defaults, or relationships, leaving the agent without guidance on how to use them.

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 uses the verb 'Analyze' and specifies the resource as 'heuristic dissectors', which gives a basic idea. However, it does not clarify what the analysis produces or how it differs from similar tools like 'protocol_enable_disable'. The purpose is vague and does not specify the output or outcome.

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 guidance is provided on when to use this tool versus alternatives such as 'protocol_enable_disable' or other capture analysis tools. There is no mention of prerequisites, typical use cases, or scenarios where enabling/disabling heuristics is appropriate.

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