seerr_get_user_requests

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

The readOnlyHint annotation already indicates a safe read operation, and the description adds the specific-user scoping. However, it does not disclose pagination behavior via skip/take, ordering, or what happens when the user has no requests, which would be useful beyond the annotation.

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 a single, front-loaded sentence with no filler words or redundant content. It communicates the core purpose immediately and earns its place efficiently.

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?

An output schema exists, so return values need not be described, and the tool is simple. However, the description omits details about pagination (skip/take), response filtering, or relation to other request endpoints, making it minimally complete for a read operation without richer context.

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 0%, and the description does not explain any parameters. While 'user_id' is implied by 'specific user' and skip/take suggest pagination, the description does not clarify how these parameters function or that skip/take are optional, leaving gaps for the agent.

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 'Get requests for a specific user' uses a specific verb ('Get'), names the resource ('requests'), and specifies the scope ('specific user'), clearly distinguishing it from sibling tools like seerr_list_request (all requests) and seerr_get_request (single request by ID).

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?

No guidance is provided on when to use this tool versus alternatives such as seerr_list_request or seerr_get_request. It does not mention that user_id is required or suggest use cases, leaving the agent to infer usage from the name and parameter schema.

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