edgarpulse_parse_filing

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool detects specific purchase patterns and produces a quantitative conviction score, and the word 'Parse' strongly implies a read-only operation. However, it does not describe response shape, error handling, permissions, or rate limits, so meaningful gaps remain.

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 a single, front-loaded sentence that states the operation, the input types, and the analytical outcome. There is no filler or repetition, and every clause contributes to understanding the tool.

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?

The tool is simple (one required parameter, no nested objects), but there is no output schema and no annotations. The description hints at an output ('quantitative conviction score') but does not explain what the response contains, how the score is structured, or what happens on invalid input. It is minimally viable but leaves the agent guessing about return values.

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 single parameter is already documented in the input schema. The description adds useful semantic constraint by specifying that the XML must be an SEC Form 4 or 8-K filing, narrowing the valid input beyond the schema's generic 'Raw SEC XML filing content'.

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 uses a precise verb ('Parse') and names the exact resources (SEC Form 4 or 8-K XML filing), then specifies the analytical target (C-suite open market cluster purchases with quantitative conviction score). An agent can immediately tell what the tool does and what it produces. The sibling tools are unrelated, so no further differentiation is needed.

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 explicit when-to-use or when-not-to-use guidance, and it names no alternatives. An agent must infer that this tool should be used whenever a Form 4 or 8-K XML filing needs parsing for cluster purchases. There are no prerequisites, exclusions, or routing instructions.

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