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

No annotations exist, so the description carries the load; it discloses privacy ("Private to you") and the contents of each entry, which is useful. It does not state ordering, pagination, or whether an empty list is possible, and read-only behavior is only implied by the verb "list".

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 compact sentences with the resource and return contents front-loaded, followed by the routing hint. No filler or repetition.

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?

With no output schema, the description usefully specifies the shape of the result (each account with progress and film count) and the privacy scope. Minor gaps around ordering and pagination keep it from a 5.

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 two schema parameters are analytics-only boilerplate (context, llm_model) and are fully documented at 100% coverage, so there is no domain parameter for the description to explain. Nothing is missing, but the description adds no value over the schema 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?

Specific verb and resource: it lists the user's brand imports on refs.video/saved, describing exactly what each entry contains (X account, progress, film count). It also distinguishes itself from the sibling get_brand by assigning that tool a different job (brand kit and films).

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?

Routes the agent explicitly: pass an id or handle to get_brand to get the brand kit and every film, which is a clear alternative-selection rule. What's missing is a direct statement of when to call this tool itself (e.g. to discover which brands were imported), though that is strongly implied.

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