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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat safety info. It adds context about data domain (private offerings) but does not disclose rate limits, pagination, or any side effects. No contradiction with annotations.

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?

Front-loaded with purpose, then parameter descriptions. Slightly verbose (e.g., 'VC and private equity intel' could be integrated), but well-organized and each sentence adds value. No wasted words overall.

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?

No output schema, and description does not explain return values or result structure. It specifies the content type (Form D private offerings) but not fields like company name, amount, date. Adequate for simple tool with 3 optional params, but could be more 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 0%; description compensates fully by explaining each parameter: state filter with examples, days_back lookback window with default, and min_amount as post-filtered minimum. Adds meaning beyond raw schema types.

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 clearly states 'Retrieve SEC Form D private offerings' with specific examples (private rounds, hedge fund launches, exempt securities filings). It distinguishes from sibling tools like get_form_13f_holdings and get_schedule_13d_activist by focusing on Form D.

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?

Implied usage for VC/private equity tracking ('VC and private equity intel'), but no explicit guidance on when not to use this tool versus alternatives like get_schedule_13d_activist. Does not mention exclusions or prerequisites.

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