library

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

No annotations provided, so description must disclose behavioral traits. It mentions 'Read or mutate' but does not describe side effects, persistence, or required permissions for mutations. Schema's 'active_only' hints at soft-delete but description omits this context.

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 sentences, no redundant words. First sentence defines scope, second adds constraint. Efficient and front-loaded.

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?

Tool has 5 parameters, multiple actions, and no output schema. Description is too minimal to cover behavioral details (return values, action-specific outcomes). Lacks completeness for an agent to reliably invoke.

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 description coverage is 100%, baseline 3. Description adds that IMDb ID and type are required for add/remove, providing context beyond schema. But other parameters (query, action, active_only) are not elaborated.

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 states 'Read or mutate the Stremio library' which clearly defines the verb and resource. However, it does not distinguish from sibling tool 'search' which may overlap with the library's search action.

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?

Description provides a usage hint for add/remove actions (require IMDb ID and type) but lacks explicit guidance on when to use this tool versus alternatives like search or play.

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