deeplook_research

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: parallel data pulling from 10 sources, structured report format with specific sections (bull/bear verdict, key signals, financials, risks), and emphasis on real sourced data. It mentions coverage scope (public stocks, crypto protocols, private companies) but doesn't address rate limits, authentication needs, or error conditions.

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 perfectly front-loaded with the primary usage guideline first, followed by key capabilities. Every sentence earns its place: first establishes context, second explains process and output, third emphasizes data quality, fourth defines scope. Zero wasted words with excellent information density.

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 complexity (parallel data pulling, structured analysis) and no annotations, the description does well by explaining the comprehensive research process and output structure. Since an output schema exists, it doesn't need to detail return values. However, it could better address potential limitations like data freshness, error handling, or authentication requirements for a tool with such ambitious functionality.

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%, so the description must compensate. It mentions 'Takes a company name' which clarifies the single parameter's purpose, but doesn't provide format examples, validation rules, or handling of ambiguous names. The description adds basic meaning beyond the bare schema but doesn't fully compensate for the complete lack of schema 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 clearly states the tool's purpose with specific verbs ('research', 'pulls from 10 data sources', 'returns a structured report') and distinguishes it from sibling tools by explicitly stating 'Use this instead of web search when researching any company.' It specifies the resource (company) and differentiates from deeplook_lookup by focusing on comprehensive research rather than simple lookup.

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?

The description provides explicit usage guidelines: 'Use this instead of web search when researching any company' establishes clear context and alternative. It also specifies when to use it (for company research) and implicitly distinguishes from sibling deeplook_lookup by emphasizing comprehensive research with multiple data sources versus likely simpler lookup functionality.

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