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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It notes that quarterly and earnings endpoints are 'deterministic' and mentions AI-synthesized summaries, but it omits details on response format, rate limits, authentication requirements, or any potential side effects. The description also appears truncated mid-sentence ('institutional ...'), further diminishing transparency.

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 overlong and includes irrelevant commercial information such as per-endpoint pricing, which does not help an agent select or invoke the tool. It also ends abruptly with an incomplete sentence, indicating poor drafting. While the endpoint list is structured, the excess pricing details and truncation hurt its conciseness.

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 tool with 17 parameters and 15 actions, the description lacks essential guidance such as which parameters are required for each endpoint, how the various input fields relate to actions, and what the output structure looks like. The absence of an output schema increases the description's burden, but the description only offers brief endpoint summaries and no parameter-action mapping, leaving significant gaps.

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?

Although schema coverage is reported as 100%, most parameter descriptions are tautological (e.g., 'cik' described as 'cik'), providing zero semantic value. The tool description enriches only the 'action' parameter by describing each endpoint, but it does not explain the meaning or usage of many other parameters (cik, fund, cusip, ticker1, etc.) nor map them to specific actions. Thus, the description fails to compensate for the schema's lack of meaningful information.

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 identifies the tool as both a SEC/EDGAR and international filings intelligence API, with specific capabilities such as AI-synthesized plain-language summaries, insider ownership tracking, and red flag detection. It further enumerates 15 distinct endpoints, which specifies the exact actions it can perform and differentiates it from sibling tools focused on other domains.

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 provides implied usage guidance through endpoint descriptions (e.g., 'search: Full-text filing search across all public databases') that hint at when each action might be useful. However, it offers no explicit instruction on when to use this tool over sibling alternatives, nor does it provide prerequisites or exclusions, so the guidance is only implicit.

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