Generate underserved content-angle hypotheses for a niche and audience, revealing gaps to guide short-form video ideation without live search-volume claims.
Generate underserved content-angle hypotheses around a niche. These are ideation hypotheses, not claims of live TikTok search-volume data.
| Name | Required | Description | Default |
|---|---|---|---|
| topic | Yes | ||
| audience | No | creators |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries full burden. It usefully discloses that outputs are ideation hypotheses rather than live data, but omits whether the tool is read-only, auth requirements, rate limits, or output format.
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, front-loaded with the core purpose and a clarification. 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?
For a simple two-parameter tool with no annotations or output schema, the description should at least explain both inputs and basic usage. It leaves the audience parameter entirely unexplained and provides no invocation guidance.
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% for two parameters. The description only loosely maps 'around a niche' to the required topic parameter and never mentions the audience parameter or its default, leaving semantics largely undocumented.
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 and output: 'Generate underserved content-angle hypotheses around a niche.' This is clear and distinguishes itself from analysis siblings, but it does not explicitly differentiate from generate_remix_ideas or other generation tools.
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?
Provides no when-to-use guidance or alternatives. The caveat 'not claims of live TikTok search-volume data' sets expectations but does not help an agent decide between this tool and siblings like generate_remix_ideas.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.