plex_get_recently_added

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

No annotations are provided, so the description carries full burden. It only states that it retrieves recently added media, without disclosing ordering, pagination, side effects, or whether the results can be filtered further. This lacks sufficient behavioral context for the agent.

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 short (2 sentences) but includes an unnecessary 'Args:' prefix. While not verbose, it omits important context that would justify its length. Every sentence provides some value, but it could be more informative.

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?

Despite having an output schema (so return values need not be detailed), the description lacks completeness given the 11 sibling tools. It does not explain how results are ordered, whether it returns all libraries or a specific one, or any constraints like authentication. The minimal description is insufficient for correct agent use.

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 input schema has 1 parameter (limit) with 0% schema coverage. The description adds the meaning: 'limit: Nombre maximum de résultats' (maximum number of results), which is helpful beyond the schema's default and type. This compensates for the lack of schema descriptions.

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 the verb and resource: 'Retrieves media recently added to the library'. It is specific to the tool's function but does not differentiate from sibling tools like plex_get_on_deck or plex_get_recommendations, which could similarly retrieve recent content.

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. There is no mention of typical use cases, prerequisites, or when not to use it.

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