Call an LCU endpoint with any verb

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

Goes beyond the annotations by disclosing the allowlist gate: GET/HEAD are always allowed, mutating verbs require matching allowlist entries, and unauthorized requests are rejected before execution. This is meaningful operational context not derivable from destructiveHint/openWorldHint. It stops short of describing the response shape or partial-failure behavior.

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?

Front-loads what the tool does, then alternatives, then behavior. Each sentence carries a distinct, decision-relevant fact and nothing is repeated from the schema.

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 generic escape-hatch tool with no output schema, the description covers purpose, alternatives, and the write-allowlist constraint. It would be stronger if it hinted at success/failure signalling or that responses are raw LCU JSON, but nothing critical to invocation is missing.

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 100%, so method, path, and body are already documented in the schema, including the pattern for path and the note that body is omitted for GET/DELETE. The description adds no parameter detail beyond that, so the baseline 3 applies.

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 (send an HTTP request with any verb) and resource (internal LCU REST endpoint), and enumerates the supported verbs. It is immediately distinguishable from lol_get, lol_eval, and the lol_workflow_* 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?

Explicitly routes the agent: prefer this over lol_eval for REST, prefer lol_get for safe reads, prefer lol_workflow_* for common automated actions, and use this for mutations or uncovered endpoints. When-to-use, when-not, and named alternatives are all present.

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