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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld. The description adds genuinely useful context beyond that: a 30-90 second latency expectation, the five-phase structure, that it fans out to 20+ tools, and that output is a McKinsey-style structured report. This materially helps an agent set expectations for a long-running call.

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?

Four sentences, front-loaded with the core action and its phases, then latency, then selection guidance. Efficient and well-ordered, though the phase/tool detail is slightly dense for the up-front position.

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?

With an output schema present, return values needn't be explained, and annotations cover the safety profile. The description supplies the remaining essentials: scope, duration, and use case. Only the lack of explicit sibling routing keeps it from a 5.

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 100%, so the schema already documents ticker, question, and template fully. The description adds only that research is performed 'on a company,' which is marginal beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ('Run a comprehensive 5-phase agentic deep research pipeline on a company') and details what the pipeline gathers and produces. An agent can distinguish this from narrowing siblings like get_deep_research_qa or get_research_briefing based on the described scope.

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?

'Use for deep-dive, multi-faceted research requests where the user wants a thorough analysis' gives clear positive selection criteria. It does not name alternatives (e.g. get_deep_research_qa, get_research_briefing) or state when NOT to use it, so it falls short of full when/when-not guidance.

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