tracearr_list_recently_added

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

Annotations already indicate read-only. Description adds valuable behavioral details: cursor pagination, ordering, server-reported added date, and include_removed behavior for tombstones. These go beyond the annotation and help set expectations.

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?

Two concise sentences: the first states the core function and ordering, the second enumerates filters and the include_removed option. No redundant information or filler.

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 list tool with output schema present, the description covers the main usage, filters, and a special behavior. It doesn't elaborate on cursor mechanics or return shape, but these are sufficiently covered by schema and standard pagination understanding.

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 has 0% param descriptions, but the description explains the purpose of key filters (server_id, library_id, media_type) and the include_removed flag. Cursor and page_size are left to standard pagination knowledge, which is acceptable.

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?

Description clearly states the tool lists library items ordered by server-reported added date, newest first, with specific filters. It distinguishes itself from sibling tools by its focus on recently added items and pagination style.

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 context for use: listing recently added items with filtering by server, library, and media type. Does not explicitly mention alternatives or when not to use, but the purpose is distinct enough among siblings.

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