tiktok_list_bundles

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

No annotations are provided, so the description carries the full burden. It states the tool lists bundles and allows overriding the default directory, implying a read-only behavior. However, it does not explicitly confirm no side effects, no destructive actions, or any limitations. The description is adequate but not thorough.

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, using just a few lines to state the purpose, parameter, and return value. Every sentence adds value with no redundant information. The format is clear and front-loaded with the main action.

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?

The description covers the tool's purpose, the single optional parameter, and the return format (JSON array with bundle summaries). Although an output schema exists, the description provides sufficient detail for an agent to understand what is returned. For a simple list tool, this is complete.

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 0%, meaning the parameter 'bundles_dir' lacks schema-level explanation. The description compensates by explaining it overrides the default directory. This adds meaningful context beyond the raw schema type, though it could specify the default behavior more precisely.

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 tool lists all prepared bundles with summary metadata. The verb 'list' and noun 'bundles' unambiguously define the action and resource. It is distinct from sibling tools that create, delete, or get individual bundles.

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 provides no guidance on when to use this tool versus its siblings (tiktok_create_bundle, tiktok_delete_bundle, tiktok_get_bundle). It does not mention prerequisites, exclusions, or typical use cases. The agent must infer from the name and context.

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