validate_streamable_http_runtime

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

With no annotations provided, the description carries the full burden of behavior disclosure. It only says it 'runs' something, without disclosing side effects, read-only vs mutating nature, auth requirements, or output format. This is a serious gap for a tool that likely performs complex validation.

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 short sentence, but it is under-specified rather than concise. It contains almost no actionable information, so the words do not earn their place. It is more of a heading than an explanation.

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?

For a tool that likely executes a multi-faceted validation matrix, the description provides no context on what the matrix entails, how to interpret results, or how the output_path is used. With no output schema and minimal description, an agent cannot confidently call this tool.

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 only parameter, output_path, has 0% schema description coverage and the description does not mention it at all. The description adds no meaning to the parameter, failing to compensate for the schema's lack of explanation.

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 states a specific verb ('Run') and resource ('Streamable HTTP'), and lists topics it covers (authorization, lifecycle, SSE, audit). However, 'repeated ... matrix' is vague and does not clearly convey what the tool actually does. It does not explicitly differentiate from sibling validation tools like validate_policy_controls or validate_multilang_pack, but the resource name gives some distinction.

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 gives no guidance on when to use this tool versus its siblings. It does not mention prerequisites, scenarios, or exclusions. An agent would have no cue for choosing this over other validation tools.

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