flipper_asset_pack

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

Annotations declare readOnlyHint=false and destructiveHint=false. The description adds that installing copies a folder to the SD card, implying a non-destructive action. It does not disclose potential side effects like overwriting existing packs, but no contradiction with annotations.

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 two sentences, front-loaded with the main action. Every sentence adds value: the first states what the tool does, the second clarifies the difference between install and selection. No wasted words.

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 explains the tool's behavior (list/install, SD card copy, device selection, reboot). However, it does not specify the return format for list or install actions, which would be helpful for an AI agent. Overall, it is mostly complete given the tool's complexity.

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 already describes all four parameters with high coverage (100%). The description adds context about asset pack types and on-device selection but does not enhance parameter-level meaning beyond the schema.

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 or installs Momentum asset packs (themes: animations, icons, fonts). The verb 'list or install' and resource 'asset packs' are specific, and the description distinguishes from sibling tools by focusing on asset pack management.

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 the two actions (list and install) and notes that selecting is done on device. However, it does not explicitly state when not to use this tool or provide alternatives, though the context of sibling tools implies its specialized role.

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