Download SIE file

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the SIE format context and fiscal-year scoping, but does not disclose further behavioral details like output encoding, file format specifics, or behavior when no export exists.

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 efficient sentence that front-loads the action and resource, then provides the necessary format context. No wasted words or redundant restatements of the title.

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?

For a simple one-parameter, read-only download with safety annotations already present, the description is largely sufficient. The only minor gap is that with no output schema, it does not specify the response format or that this returns a file rather than JSON, though the word 'Downloads' and 'SIE export' strongly imply it.

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 description coverage is 100%, so the schema already documents fiscalYearId as a path parameter. The description reinforces that the download is 'for a fiscal year' but adds no additional parameter syntax, constraints, or value semantics beyond that.

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 states a specific verb ('Downloads') and a specific resource ('SIE export'), and clarifies that resource by naming the Swedish standard accounting interchange format. This clearly differentiates it from the many sibling download tools by the unique resource type.

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 implies use when an accounting export for a fiscal year is needed, but it does not explicitly state when to prefer this over related tools such as get_fiscal_year or list_fiscal_years. No alternatives or exclusions are mentioned, leaving the usage context to inference.

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