generate_hooks

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

No annotations provided, so description carries full burden. It discloses persistence to hook library, cost model ('each batch of 3 candidates spends one AI credit'), potential for fewer results due to credit cap, and the necessity of a valid profile_id. All key behavioral aspects are covered.

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?

Every sentence contributes essential information: purpose, usage, scoring, persistence, cost, error behavior, prerequisite. No redundancy or fluff. Front-loaded with main purpose.

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 tool with 3 parameters and no output schema, the description fully explains what is returned (hooks ranked by virality score), cost implications, and possible outcomes. No gaps remain for selection or invocation.

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 100%, but description adds extra meaning: cost per count, truncation of direction field to 500 chars, and reinforcement of profile_id source. This adds value beyond the schema descriptions.

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 clearly states 'Generate scored TikTok hook candidates for one of the user's Svmmon profiles.' The verb 'generate' and resource 'hooks' are specific. It distinguishes from siblings like generate_slideshow, list_profiles, etc., which are clearly different tasks.

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 says 'Use when the user asks for hooks, openers, or angles for a profile' with an example. Provides prerequisite: 'Requires a valid profile_id: call list_profiles first and never invent one.' This gives clear context on when to use and necessary preconditions.

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