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

With no annotations provided, the description carries full behavioral burden. It transparently discloses the $1.00 cost, the required Stripe Shared Payment Token, and the Authorization header format, which are critical operational details beyond the schema. It also lists the 12 research steps, providing clarity on the processing scope.

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 tool's purpose, followed by a compact list of research steps and then the cost/payment details. Every sentence contributes essential information with no redundancy, making it concise and well-structured.

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 simple single-parameter input and absence of output schema, the description covers the essential aspects: purpose, research content, cost, and payment mechanism. It could benefit from stating expected return format, but the tool's name and step list make the output obvious enough for most use cases.

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 already fully documents the single 'ticker' parameter with a clear description. The tool description adds no additional parameter semantics, so it does not go beyond the schema's baseline coverage.

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 retrieves fundamental analysis and enumerates the specific research steps covered, giving a precise scope. However, it does not explicitly contrast with sibling tools like get_company_primer or get_investment_memo, so it lacks direct differentiation.

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 no guidance on when to prefer this tool over alternatives such as get_company_primer or search_research. It only states what the tool does and its cost, leaving the agent to infer usage context.

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