Raw Longhorn API request

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

With no annotations present, the description carries the full safety burden and does well: it discloses read-only mode behavior, the safety of GET, and the destructive nature of POST/PUT/DELETE. It does not disclose response/error behavior or body-construction expectations, but the core behavioral risks are clearly communicated.

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 front-loaded with the primary purpose and remains tight for the amount of safety-critical guidance it conveys. Each clause earns its place, and the message is direct without repeating 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?

The tool is intentionally open-ended, so a fully deterministic description is impossible. The combination of schema and description gives enough to select endpoints and understand safety, though it could add a note about response shape or how to form the request body for non-GET calls.

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 schema already documents method, path, and a generic body object, with only 33% schema description coverage. The description adds meaningful method-level semantics by marking GET as safe and mutating methods as destructive, but it does not explain how or when to populate body beyond the generic 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?

The description clearly states that this is an escape hatch for Longhorn API endpoints not covered by a named tool, which distinguishes it from the many sibling tools. The title and description together make the tool's purpose unambiguous: issue a raw request to the Longhorn API.

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 explicitly says to use this when an endpoint is not covered by a named tool, which sets the boundary with remaining siblings. It also gives clear usage constraints: GET is safe, mutating methods require explicit user authorization, and read-only mode rejects non-GET requests.

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