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

With annotations already declaring readOnlyHint=true, openWorldHint=true, and destructiveHint=false, the description adds substantial context: SEC-verified citations versus caller-asserted context, $25/call pricing, and ~60s latency. These are meaningful behavioral details an agent needs before invoking an expensive, long-running analysis.

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 with the core purpose and then supplies the lens list, optional inputs, and commercial/runtime facts. It is appropriately sized for a flagship expensive tool, though the long lens enumeration and dense opening sentence keep it from being maximally concise.

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?

For a complex report-generation tool with no output schema and sparse parameter documentation, the description covers the report structure, provenance, optional inputs, cost, and expected duration. It does not describe the returned format or citation layout in detail, leaving a modest completeness gap.

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, and it does for the optional parameters: it gives a concrete market example and explains that context is caller-supplied deal material treated as unverified. Ticker is self-evident, though the market object's accepted keys and context string constraints are not fully specified.

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 defines a specific resource and output: an eight-lens institutional analysis of a US-listed company grounded in SEC-verified figures. It is unmistakably different from siblings such as sec_extract or validate_financials, but it never explicitly contrasts itself with those alternatives, so it stops short of a 5.

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 lens list and 'flagship' framing imply when this tool is appropriate, and it explains how optional market/context inputs extend the analysis. However, it gives no explicit when-not-to-use guidance and does not name sibling tools as alternatives for narrower tasks like raw SEC extraction or validation.

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