research

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

No annotations provided, so description carries full burden. Only mentions cost and network (Base via x402) but no disclosure about side effects, authorization needs, or whether it makes external calls. No safety or behavioral traits described.

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?

Single sentence including cost info is concise. However, conciseness sacrifices essential details; it is efficient but incomplete.

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?

No output schema, no explanation of return values. The description is insufficient for an AI agent to understand the tool's behavior without external documentation. Parameter help is minimal.

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 input schema has 100% coverage but the description adds no meaning beyond a free-form object pointer to an external URL. The description does not summarize expected input structure or provide examples, leaving agents with minimal guidance.

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?

Description states 'Structured intel brief — web research + analysis', indicating it performs research and produces a brief. However, it doesn't clearly distinguish from sibling tools like 'intelligence_report' or 'delphi', and the verb 'research' is generic.

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 on when to use this tool vs alternatives. The description only mentions cost but does not specify prerequisites, when not to use, or how it differs from similar tools.

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