list_hubs_home_recently_added

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint, so the safety profile is covered. The description adds only the GET endpoint, which is more of an implementation detail than a behavioral disclosure; it does not describe response characteristics, pagination, or any scoping constraints.

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 concise and front-loaded with the purpose. The endpoint line adds a useful exact path without wasting words, making it appropriately sized for a simple zero-parameter operation.

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 zero-parameter, read-only endpoint with an output schema and strong annotations, the description is mostly complete. It identifies the resource and endpoint clearly, though a little more context about what 'home hubs' are and how this differs from similar hub tools would make it 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?

The tool has zero parameters and 100% schema description coverage, so the description has no parameter burden. The baseline of 4 for a no-parameter tool is appropriate.

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 clear action and resource: 'Get home hubs Recently Added' and provides the exact endpoint GET /hubs/home/recentlyAdded. It is not tautological, but it does not explicitly distinguish this from closely related sibling tools like list_hubs, list_hubs_continue_watching, or list_library_recently_added.

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?

The intended use is implied by the resource name: use this when you need the 'Recently Added' hub from home. However, there is no explicit guidance about when to prefer this over the many sibling hub/list tools, and no exclusions are mentioned.

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