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

With no annotations, the description carries the full behavioral burden and discloses almost nothing: no auth requirements, no rate limits, no pagination behavior, no indication of what 'every data point' actually means in the response. The only implicit signal is that this is a read/retrieval operation, which is minimal.

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?

Two short sentences with no filler, and the core capability is stated first. It is compact to the point of under-specification rather than bloated, so it earns credit for tightness but not a 5.

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?

A four-parameter retrieval tool with no output schema and no annotations should explain what is returned and how size/startDate shape the result set, and it does none of that. Given the complexity signals and the absence of structured support, the description leaves 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?

Schema coverage is 100%, so the baseline is 3, and the description genuinely adds value by enumerating the valid family values (form-144, form-13f, form-13d-13g, form-d, form-c, reg-a, n-port, n-cen, n-px), which the schema's bare 'form family' field lacks. It does not elaborate on cik, size, or startDate, but the enum addition lifts it above baseline.

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 conveys the resource (parsed XML form data with 'every data point') and scopes it to a set of form families, but it is a noun phrase with no verb, and it never distinguishes itself from close siblings like form_13f_holdings, xbrl_to_json, or search_filings. An agent can guess it retrieves structured form content but cannot confidently separate it from those alternatives.

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?

There is no when-to-use, when-not-to-use, or alternative-routing guidance at all. The listed form families function as allowed parameter values, not as usage conditions, so the agent gets no help deciding between this and the many sibling filing tools.

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