Parse HTTP/2 frames

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'parse' and 'including common frame payloads,' but does not explain output format, error behavior, supported frame types, or whether any transformation is applied. This is minimal added transparency beyond the schema.

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, front-loaded sentence with no filler. Every word contributes to the core purpose, and it is appropriately sized for a simple one-parameter tool.

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 there is no output schema, no annotations, and a complex binary protocol being parsed, the description is too sparse. It does not enumerate supported HTTP/2 frame types, how results are structured, or how multiple frames are delineated in the input, leaving major gaps for an agent to invoke it correctly.

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 description coverage is 0%, so the description must compensate for the single inputHex parameter. It adds 'from hex,' but does not clarify accepted hex formatting (e.g., whitespace, 0x prefixes, uppercase/lowercase), payload constraints, or examples, leaving significant ambiguity.

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 parses raw HTTP/2 frames from hex, with a specific verb ('parse') and resource ('HTTP/2 frames'). It also notes coverage of common frame payloads, which distinguishes it from siblings like grpc_frame_parse and network_http2_fingerprint.

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 on when to use this tool versus alternatives. The description implies its purpose but does not mention related tools such as grpc_frame_parse for gRPC frames or proto_dissect_http for HTTP, leaving the agent without decision context.

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