get_recently_added

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

The description merely restates the tool name, adding no behavioral detail beyond what the annotations (readOnlyHint=true, destructiveHint=false) already convey. It does not explain the meaning of 'recently added' (e.g., time frame, media type) or what the response contains.

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 extremely brief, consisting of only three words, but it is redundant with the tool name. It does not earn its place by providing any new information or context.

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 simple, but the description leaves ambiguity about what 'recently added' refers to and lacks any explanation of the return value, which is especially problematic given there is no output schema. Sibling tools with similar purposes make the lack of context more significant.

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 fully documents the single 'limit' parameter with type and default. The description adds no additional meaning or usage hints beyond the schema, so it meets the baseline for this dimension.

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 uses a specific verb ('Get') and resource ('recently added media'), making the primary function clear. However, it does not distinguish this from sibling tools like get_recently_watched or get_on_deck, which could also return recently added items in different contexts.

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 information is provided about when to use this tool versus alternatives such as get_library_items or get_recently_watched. The description lacks any contextual or exclusionary guidance.

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