research_topic

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

No annotations are provided, so the description must carry the full burden. It discloses the cost and payment method ($0.001 USDC via x402), which is useful, but it does not mention whether the operation is read-only, what side effects occur, what inputs are needed, or what the output looks like. This is a significant gap.

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 very short and front-loaded, which is structurally concise. However, it sacrifices essential information for brevity, making it closer to under-specification than effective conciseness. It is not as bad as a one-word tautology, but it barely earns its place.

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?

Given the tool's ambiguous name, lack of annotations, no output schema, and generic parameter container, the description is severely incomplete. It does not explain what research means, how the tool should be invoked, or what results to expect. This is inadequate for a tool with such little structured context.

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 only exposes a generic 'params' object with no specific fields. The description adds no parameter details, so the agent has no idea what parameters are expected. Despite the schema coverage being marked high, the schema itself is uninformative; the description fails to compensate.

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 says 'research topic — Web & SEO tool', which identifies a domain but not a specific verb or action. It is essentially restating the tool's name with a broad category label. It does not clearly distinguish the tool from siblings like web_scrape, summarize, or keywords.

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 for when to use this tool versus alternatives. The description merely states the category and cost without any context about appropriate use cases, prerequisites, or exclusions.

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