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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds the scope that only public workflows are listed and that they are importable, which is useful context beyond the annotations. However, it does not disclose pagination behavior, response structure, or any filtering nuances beyond the schema, so the added value is moderate.

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 a single, focused sentence. It states the subject, action, and key qualifier ('public', 'can be imported') without wasted words or redundancy. It is front-loaded and immediately comprehensible.

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 list operation with four optional parameters, full schema descriptions, and a safety profile covered by annotations, the description is sufficiently complete. It clarifies that these are public workflows intended for import, which is the key context for using the tool. The presence of an output schema further reduces the need to describe return values.

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 input schema provides 100% coverage, with each parameter (limit, offset, search, trigger) having a clear description. The tool description itself does not add parameter-level guidance, but the schema already does the heavy lifting, so the baseline of 3 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 clearly states the action (List), the resource (public BlitzReels workflows), and the purpose/capability (can be imported into a workspace). It distinguishes from sibling tools like workflows_get (retrieves a single workflow) and workflows_import (performs the import), making it obvious this is a discovery/browsing endpoint.

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 implies the use case: finding public workflows to import. It does not explicitly name alternatives or provide when-not-to-use guidance, but the context is clear and the sibling tool names (workflows_import, workflows_get) subtly signal the workflow lifecycle. No exclusions are mentioned, but for a simple list operation this is adequate.

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