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

With no annotations provided, the description must fully disclose behavior. It mentions that the tool searches, reads, and produces citations, but doesn't explain how it works, what intermediate steps occur, whether it's safe/read-only, or what the citation format looks like. This is significant for a tool that appears to combine multiple operations.

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 extremely concise with no filler, but it's under-specified. It's a fragment rather than a complete explanation, sacrificing clarity for brevity. Very short but 'appropriately sized' would include at least enough detail to be useful.

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 no annotations, no output schema, and minimal parameter info, the description is inadequate. The agent is left without understanding the tool's workflow, return value, or integration with other contexts. Given the existence of more specialized siblings, this high-level research tool requires more detail to be used correctly.

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% and the description provides no additional meaning for the parameters beyond their names. The tool doesn't explain what 'query' should contain or how 'max_results' affects the output, leaving the agent to guess based solely on parameter names.

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 'Search + read with citations' indicates a combined search-and-read operation with a citation output, but it's vague about the specific resource or domain. It provides some differentiation from simpler siblings like web_search or read_url, but lacks the specificity of a clearly defined verb+resource tool.

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?

No guidance is provided about when to use this tool versus alternatives. With many sibling tools like web_search, read_url, and agent_research, there is no indication of when research_topic is the right choice or what distinguishes it.

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