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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond the annotations: 'no credits consumed' (a cost trait not expressible in annotations) and that enabled tools are usable from ANY project via dreamagent_chat. It does not cover rate limits or output shape, but with an output schema present that is acceptable.

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?

Front-loads the identity and payload in sentence one, then usage in sentence two. The parenthetical tool enumeration is long but earns its place by telling the agent what 'superpowers' concretely means. Slightly wordy overall, but no sentence is filler.

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 an output schema present, return values need not be described, and the description still previews the key returned fields (enabled state, beta pricing). It covers what the tool is, when to call it, and what to do next, which is everything an agent needs for a zero-param list tool.

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 tool takes zero parameters, so there is no parameter semantics to explain; the baseline for a 0-param tool is 4. The description correctly implies no filtering or scoping input is required.

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?

States a specific verb (List) and resource (DreamAgent Superpowers) and immediately enumerates what those are — song/video/image generation, voiceover, lip sync, voice clone, transcription, media processing, PDF tools — plus the returned fields (enabled state, beta pricing). This is clearly distinguishable from siblings like dreamagent_list_projects or dreamagent_list_global_integrations.

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?

Gives three explicit triggering conditions (what tools are available, whether a specific tool is enabled, what can be added to a project) and routes the agent onward to dreamagent_chat for actual invocation. It does not state any when-not condition or prerequisite, but the context is unambiguous.

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