Raw API request

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

With no annotations supplied, the description carries the disclosure burden. It does disclose the write-permission gate and the undocumented nature of the API, which is useful. However, it does not describe response shape, error behavior, or side effects beyond method restrictions.

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?

Three short sentences, each earning its place. The core purpose is front-loaded and the write restriction is stated clearly. No redundant or filler content.

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?

The description gives enough to start calling the tool and explains the key access constraint dropped by the schema. But since there is no output schema and no annotations, it should ideally warn that response formats are unknown or that arbitrary requests may behave unpredictably.

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 only 25%, so the description must compensate for the undocumented body and query parameters, but it does not explain them. It adds one useful parameter-specific constraint—GET vs. write methods—but leaves most parameter semantics to inference.

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 identifies this as an escape hatch for endpoints the server does not wrap, which distinguishes it from the dedicated sibling tools. It could be more explicit that it makes an arbitrary BandLab HTTP request, but 'this is how you explore it' conveys the main purpose well.

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?

It says the tool is for endpoints not yet wrapped, which implies using sibling tools for wrapped endpoints. It also gives a concrete condition: GET is always allowed, while other methods require writes to be enabled. This is practical guidance, though it does not explicitly name alternatives.

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