raw_request

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

Discloses that path must start with slash and is appended to base URL, but does not mention potential side effects of methods like DELETE or POST that modify state. With no annotations, description carries full burden but lacks depth.

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?

Concise: one sentence for purpose, one for when-to-use, and two example calls. No extraneous words, front-loaded with core intent.

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?

Covers core functionality, usage guidance, and examples. Though missing detailed error handling or response format, output schema exists to fill gaps. Sufficient for an escape hatch 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?

Despite 0% schema coverage, the description adds meaning by explaining path format and providing usage examples for method and json_body, going beyond raw schema.

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?

Clearly states the tool as an 'escape hatch' to send arbitrary requests to the LM Studio REST API. Distinguishes from siblings by specifying it is for endpoints not covered by dedicated tools.

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 tells when to use ('when you need an endpoint not covered by a dedicated tool') and provides examples, effectively guiding the agent to avoid misuse.

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