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

The description goes far beyond the annotations by disclosing that nothing is saved, no draft/article/file is created, API key and credits are consumed per call, results are non-deterministic, and it returns prose to read with a warning to verify factual claims. This richly supplements the readOnlyHint, openWorldHint, and idempotentHint annotations without contradiction.

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?

The description is front-loaded with the core action, then efficiently uses two more paragraphs for usage distinction and behavioral caveats. Every sentence carries meaningful information with no filler, and the structure makes key facts easy to scan.

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 generative research tool with one parameter and no output schema, the description explains the return content (insights, sources, outline), return format (prose, not JSON), runtime characteristics, cost implications, and non-determinism. It is fully sufficient for an agent to understand what to expect and how to act on the results.

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 schema already provides 100% coverage for the single 'query' parameter, including length constraints and specificity advice ('Specific beats broad'). The description adds little beyond the generic 'topic' wording, so it neither improves nor detracts from the schema's clear parameter documentation.

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?

The description opens with a specific verb and resource: 'Research a topic with AI and return insights, sources, and a suggested content outline.' It clearly distinguishes from siblings by stating it is raw material, not a finished article or title, and explicitly points to generate_title_seo and search_articles for those needs.

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?

It gives explicit when-to-use guidance: 'Use it at the START of a piece, before drafting — it produces raw material to write from, not a finished article and not a title.' It also names alternatives for titles and existing content checks, and warns that it runs longer than a plain read, implying it is not for quick lookups.

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