fetch_filed_document

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

No annotations provided, so description carries burden. It discloses download behavior, return values (local path, text), and special handling for shareholder lists (table parsing). However, it does not mention auth needs, rate limits, or side effects (though presumably read-only). Adequate but not comprehensive.

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 two short paragraphs. First sentence states core purpose, second adds behavioral details. No extraneous text. Front-loaded and efficient.

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?

Despite no output schema, the description explains return values. But with 4 parameters and low schema coverage, leaving three unexplained is a significant gap. The relationship to list_filed_documents is helpful, but overall incomplete for parameter usage.

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 0%, so description must compensate. It explains the category parameter in detail (substring matching, examples), but does not describe company, which (default 'latest'), or match (default 'exact'). Only 1 of 4 parameters gets meaningful explanation.

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 a filed document from the DK document register, specifying verb, resource, and context. It distinguishes from siblings like list_filed_documents (listing vs downloading) and fetch_document (different register implied).

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 provides context on category matching (case-insensitive substring) and gives examples, but does not explicitly state when to use this tool vs alternatives like fetch_document or list_filed_documents. Missing when-not-to-use guidance.

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