get_media_details

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

With no annotations, the description carries the full behavioral burden, and it does well by explaining the media/season status enum, the Seerr vs legacy Overseerr difference for code 6, and that request statuses are separate. It does not mention auth, side effects, or return shape, but the status-code clarification is genuinely valuable for correct interpretation.

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 compact and front-loaded: the core action comes first, followed by the non-obvious status caveats. The status-code detail is longer than typical, but it earns its place because the enum has version-specific meanings.

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?

With 7 parameters, no output schema, and no annotations, the description covers the main status-code ambiguity but leaves gaps: it does not explain what the returned payload looks like, how level values affect output, or how single vs batch selection behaves in practice. It is adequate for basic invocation but not fully self-sufficient.

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 86%, so the baseline is 3. The description reinforces the level enum and single/batch intent, but it adds little beyond the schema for parameters like format, fields, language, or items. The status-code block applies to returned data, not to parameter meaning.

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 concrete verb and object ('Get media details') and immediately states single/batch and level-control modes, so an agent knows what the tool does. It does not explicitly contrast itself with sibling get_service_details, which also fetches 'details', so differentiation is left largely to the name.

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?

There is no guidance on when to use this tool versus get_service_details, search_media, request_media, or get_services. No exclusions, prerequisites, or decision rules are given; the only usage signal is the implied purpose from the name and opening sentence.

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