historical_backfill

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

With no annotations, the description carries the full burden. It states the download action but does not disclose side effects such as whether data is overwritten, whether authentication or rate limits apply, or what 'local storage' entails. This is insufficient for a tool that writes data.

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 concise sentence with a clear verb and object, front-loaded and free of jargon or unnecessary words. It earns its place despite being terse.

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 has moderate complexity with three parameters and no annotations, and the description is too minimal to support correct invocation. It lacks usage criteria, parameter details, and behavioral implications, making it incomplete for an agent.

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 schema has zero descriptions for its three parameters, and the description does not compensate. It only hints that 'UK/ESEF' relates to the source enum, but does not explain company_id or limit. The meaning must be inferred from parameter names.

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 states the tool downloads UK/ESEF structured filing history into local storage, naming a specific verb (download), resource (filing history), and scope (UK/ESEF). This differentiates it from sibling tools like filings_list or filing_read that focus on viewing or querying, not bulk downloading.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention any exclusions, prerequisites, or comparisons to sibling tools such as filings_list or historical_facts_query, leaving the agent without usage context.

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