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

Annotations already declare this as a safe, read-only, idempotent, non-destructive operation. The description adds valuable behavioral context beyond that: it says it assembles 15+ data sources and produces an AI-synthesized narrative with specific sections. It does not mention latency, cost, or auth requirements, but the annotations cover the safety profile.

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 front-loaded, moving from purpose to output contents to templates in four efficient sentences. The template list repeats the schema enum, which is slightly redundant, but the short_thesis usage note earns its place. Overall it is appropriately sized for a multi-purpose research generator.

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?

An output schema exists, so return values need not be explained in detail; the description still usefully names the narrative sections. Annotations cover the safety profile, and the schema fully documents parameters. The main remaining gap is lack of sibling differentiation against the many adjacent research tools, which 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 baseline is 3 even without extra parameter detail. The description adds meaning beyond the schema by stating the 6-18 month horizon for the short_thesis template, which is not present in the enum description. It does not add similar guidance for focus or ticker, but those are fully documented in the schema.

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 uses a specific verb and resource: generate a comprehensive investment research briefing for a company. It clearly states the output contents and template options, distinguishing it from generic research tools. However, it does not explicitly contrast itself with similar sibling tools such as get_deep_research or get_board_briefing.

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 gives one explicit usage rule: use short_thesis for bear case analysis with a 6-18 month horizon. It lists the five available templates, which helps selection. But it does not state when to use this tool instead of the many other research and briefing siblings, nor when not to use it.

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