list_meme_hooks

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

No annotations provided, so description carries full disclosure burden. It adds domain context explaining what meme hooks are (duration, purpose), but omits safety profile (read-only vs mutation), rate limits, or pagination behavior details that annotations would normally cover.

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 sentences with zero waste: first defines resource and its characteristics, second provides usage workflow guidance. Every word earns its place; appropriately front-loaded.

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 listing tool with no output schema, description compensates by identifying the key output field to capture (memeHookName) for use with create_short. Covers pagination via schema. Good completeness for a simple list operation.

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 has 100% description coverage with clear pagination parameter descriptions ('Page number', 'Items per page'). Description adds no parameter-specific guidance, which is acceptable given schema completeness, meeting baseline expectation.

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?

Description provides specific verb 'List' with resource 'meme hook clips', defines what they are (2-5 second attention grabbers prepended to shorts), and distinguishes from siblings like list_music or list_templates by specifying the unique clip type and its relationship to video creation.

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?

Explicitly connects to sibling workflow by stating to 'Use the exact memeHookName when creating shorts', establishing when/why to use this tool (to get valid names for create_short). Lacks explicit 'when not to use' or alternative guidance.

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