list_library_recently_added

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds the global scope and exact endpoint but does not disclose behavior like pagination, ordering, or default limits. With annotations present, this level of added context is acceptable though not extensive.

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 exceptionally concise: one sentence plus the endpoint. Every element is useful, with the primary action front-loaded and no filler. It is appropriately sized for a zero-parameter GET endpoint.

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 simple parameterless GET with an output schema present, the description provides the essential information: the global scope and the endpoint. It doesn't clarify result ordering or how this endpoint relates to other recently-added variants, but the tool's simplicity and existing structured data make this adequate.

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 tool has zero parameters and the input schema is empty, so 100% schema coverage. With no parameters to document, the description has nothing to add; the baseline for 0 parameters is 4.

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 states a specific verb and resource: 'Get Global Recently Added' with the endpoint 'GET /library/recentlyAdded'. The word 'Global' clearly distinguishes this from sibling tools like get_library_sections_by_section_id_recently_added, so an agent can tell them apart without further investigation.

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 about when to use this tool versus alternatives such as list_hubs_home_recently_added or get_library_sections_by_section_id_recently_added. The description only states what it does, leaving the agent to infer usage context from the name and endpoint rather than explicit when-to-use or when-not-to-use conditions.

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