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

The annotations already cast this as a non-read-only, non-destructive, non-idempotent submission, and the description reinforces that by noting the request goes to a human team, which implies a durable side effect rather than a lookup. The confirmation requirement ('only after the user agrees') is genuinely useful behavioral context that the annotations cannot express. What is missing is what happens after submission, e.g. whether the user gets a response or tracking, and whether duplicate ideas are merged or rejected.

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 the core action first, the trigger condition second, and the optional detail last, so nothing important is buried. There is no filler and no restatement of the title.

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 two-parameter submission tool with an output schema and full annotation coverage, this covers the action, the trigger, the user-consent gate, and the optional payload detail. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100%, so the baseline would be 3, but the description adds real meaning by narrowing the optional link to TikTok or Instagram examples of the trend, which is more specific than the schema's generic 'optional https link'. It also implicitly frames 'idea' as a trend or concept pitch rather than a template name.

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?

A concrete verb-and-resource pair ('Send MakeViral a trend or idea that has no template yet') with the resulting action explained ('so the team can add it'). It also distinguishes itself from the sibling tool that otherwise looks similar, search_templates, so an agent can choose between them without opening a schema.

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?

This gives an explicit trigger ('when search_templates finds nothing that fits') and an explicit gate ('only after the user agrees'), so both the condition for calling and the condition for not calling are spelled out. It also tells the agent what to include ('the TikTok or Instagram link ... when the user has one'), which is a usage instruction, not just a parameter restatement.

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