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

With no annotations, the description carries the burden and does well: it explicitly discloses $2 cost, the need for a Stripe Shared Payment Token, and the exact Authorization header format. It doesn't cover error handling or response format, but the primary side effect (payment) is transparent.

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?

Three dense sentences: purpose and contents, cost, and payment mechanism. Every sentence earns its place and the critical information is front-loaded. No repetition or fluff.

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 single-parameter paid research tool, it covers what the memo contains, the cost, and how to pay. No output schema exists, so return format is not explained, and there is no sibling guidance, but the core operational context is sufficiently complete.

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 coverage is 100% and the only parameter 'ticker' is described as 'Stock ticker symbol'. The description adds no extra parameter-level details (e.g., formatting, case sensitivity), so with high schema coverage the baseline of 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?

Description opens with 'Get a full investment memo', a specific verb+resource, and enumerates detailed content (DCF valuation, moat analysis, etc.) that clearly separates it from sibling research tools. The scope and nature ('Equivalent to a sell-side initiation note') further sharpen the purpose.

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?

It does not explicitly name alternatives, but 'Equivalent to a sell-side initiation note' gives context for when a deep full-memo is appropriate. Cost and payment instructions are practical usage guidance, though it lacks a direct 'use this instead of X' comparison.

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