dashbrr_set_overseerr_request_status

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

Annotations already indicate a destructive mutation (destructiveHint: true, readOnlyHint: false). The description adds valuable behavioral constraints: the type-prefix requirement for `instance_id` ('must be type-prefixed, e.g. `overseerr-0`') and the exact status code mapping. These details go beyond the annotations and help the agent understand the expected input and operation. No contradiction with annotations.

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 composed of three short, information-dense sentences. It leads with the primary purpose, then adds parameter details in the order they appear in the schema. Every word earns its place; there is no repetition of schema types or annotations. Perfectly concise and well-structured.

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 destructive action tool with no output schema and three required parameters, the description is nearly complete. It explains all inputs and their origins, and the annotations cover safety expectations. It stops short of describing the response format or edge cases (e.g., what happens if the request isn't pending), but this is not critical for basic invocation. Overall, the description is sufficiently complete for the tool's complexity.

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 descriptions are completely absent (0% coverage), so the description carries full responsibility. It explicitly explains all three parameters: `instance_id` format, `request_id` provenance (from dashbrr_get_overseerr_requests), and `status` numeric mapping. This clarifies the otherwise opaque string/integer types and provides the enum-like values even though no enums are declared.

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 opens with a specific action: 'Approve or decline a pending Overseerr media request.' It clearly identifies the resource (Overseerr media request) and the verb (approve/decline), distinguishing it from sibling read-only get_* tools and delete_* tools. The rest of the description reinforces purpose by detailing the required parameters.

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?

Provides clear usage guidance: `request_id` comes from dashbrr_get_overseerr_requests, establishing a specific workflow. It also specifies allowed status values (`2` or `3`). While it doesn't explicitly mention alternatives or when not to use it, the sibling context and the tool's unique action make the intended use unambiguous.

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