stremio_get_library

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

With no annotations, the description carries the full behavioral burden. It does add real value by disclosing that include_removed returns soft-deleted entries and that watch history lives there, which is non-obvious. But it says nothing about authentication requirements, whether soft-deleted items are merged into the default result, or how large the listing can get.

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?

Front-loaded with the core action in the first sentence, followed by one compact sentence per parameter. No filler, though the parameter notes are packed into a paragraph where a short list would scan faster.

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?

An output schema exists, so return-value documentation is unnecessary, and all three optional parameters are covered. What remains thin is the behavioral side: read-only nature and result size are not stated, and with no annotations there is no structured fallback for that information.

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 coverage is 0%, and the description fully compensates: it explains include_removed's soft-delete semantics, gives the accepted values for content_type ('movie' or 'series'), and enumerates watched ('any', 'yes', 'no') with its sentinel value. The schema has no enums at all, so these value lists are only available here.

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?

"List the account's library titles" states a specific verb and resource, and the added qualifiers (include_removed, content_type, watched) confirm it is a filtered listing. It does not, however, distinguish itself from siblings such as stremio_continue_watching or stremio_search_all_catalogs, which an agent could plausibly confuse with a library listing.

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 description explains what each modifier does but never states when to pick this tool over the many adjacent ones (continue_watching, browse_catalog, search). Usage is implied by "account's library titles" rather than made explicit, and no exclusions or prerequisites are given.

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