xbrl_load_filing

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

Annotations indicate not read-only and not destructive. Description adds the entry point behavior and explains return of a filing_id for subsequent use. No contradictions 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?

Concise at 4 sentences, each adding critical information. Front-loaded with action and context, no 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?

With many sibling tools, the description adequately positions this as the entry point. Covers input types, return value, and usage order. Output schema exists, so return explanation is sufficient.

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?

The main parameter 'params' is an object with properties described in the schema; however, schema description coverage is 0% for the top-level. The tool description summarizes the purpose of the parameter and its fields, adding value beyond the schema.

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?

Clearly states it loads XBRL/iXBRL filings, specifies accepted input types (local paths, HTTP/HTTPS URLs, ZIP archives), and describes return value (filing_id and summary). Distinguishes itself from siblings by being the entry point.

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?

Explicitly instructs to call this first before other tools, establishing a clear usage order. Does not mention when not to use or alternative methods for already loaded filings, but entry point status makes this less critical.

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