xbrl_edgar_bulk_facts

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

Adds behavioral context beyond annotations: returns most recent value, no filing load required. Annotations already declare readOnly, idempotent, openWorld. Description does not contradict annotations and adds useful output format info.

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?

Extremely concise: two sentences plus a docstring that front-loads purpose. No wasted words.

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?

Covers input, output format, and behavioral nuance (no filing load). Has output schema, so return value description is sufficient. Could mention limitations like max 10 items, but not essential.

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 has descriptions for ciks and concepts, and description redundantly mentions 'List of CIKs, list of concepts, taxonomy'. Since schema description coverage is actually high (despite 0% signal), the description adds marginal value. Baseline 3 applies.

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 verb (download), resource (fact data for multiple concepts and companies), and output (matrix of company × concept with most recent value). Distinguishes from siblings like xbrl_company_facts which is likely single-company.

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?

Provides context ('No filing load required') hinting at when to use, but lacks explicit when-to-use vs alternatives like xbrl_company_facts or xbrl_edgar_search. No when-not or exclusions.

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