http_prompt_configure

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

With no annotations, the description carries the full burden. It discloses one useful trait — that settings persist for the session — but says nothing about whether values are merged or overwritten, whether existing headers are replaced, whether auth is required, or what state changes result. For a mutation tool this is a substantial gap.

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?

A single front-loaded sentence with no filler, which is efficient. It is arguably thin for a tool with nested object parameters, but there is no wasted text to penalize.

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?

No output schema exists, and the description does not state prerequisites, the effect of the default session_id, or any return/confirmation behavior. For a mutation tool with zero annotation coverage and nested object inputs, the description is too thin to let an agent invoke it confidently.

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 coverage is 67%: 'params' and 'headers' carry descriptions while 'session_id' is documented only by its default. The description paraphrases those two fields ('headers or query parameters') without adding format, merge, or override semantics. Baseline 3 is appropriate where the schema does most of the work.

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?

States a specific verb ('Sets') and resource ('persistent headers or query parameters') with a clear scope ('for the session'). An agent can distinguish it from http_prompt_execute or http_prompt_init by the fact that it mutates configuration, but the description never names or contrasts with those siblings.

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?

There is no when-to-use guidance, no stated prerequisites (e.g. whether the session must first be created via http_prompt_init), and no mention of alternatives. The word 'persistent' implies the scope of effect but gives the agent nothing to route on.

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