Retrieves ELSTER transmission history for selected years and optionally downloads associated PDFs, enabling review of past tax form submissions and document retrieval.
Reads "Übermittelte Formulare" (transmission history) from ELSTER. Optionally downloads PDFs.
| Name | Required | Description | Default |
|---|---|---|---|
| years | No | ||
| downloadPdfs | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description must carry full burden. It indicates a read operation with optional download, but does not disclose side effects, permission requirements, or whether downloading modifies state. Minimal transparency beyond the obvious.
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?
Description is concise (one sentence) but sacrifices detail. It is front-loaded with the main action, but could usefully add more information without becoming verbose.
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?
Given 2 parameters, no output schema, and no annotations, the description is incomplete. It does not explain years, return format, or prerequisites (e.g., valid session). Among many sibling tools, more context would help.
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 describes two parameters (years, downloadPdfs) with 0% description coverage. The tool description hints at 'downloads PDFs' but does not explain the years parameter or its purpose. No parameter-level documentation provided.
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 it reads transmission history from ELSTER and optionally downloads PDFs. The verb 'reads' and resource 'transmission history' are specific. However, it does not explicitly differentiate from sibling tools like elster_sync_inbox, though the name suggests history vs inbox.
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 on when to use this tool vs alternatives. Does not mention prerequisites, ideal scenarios, or when to avoid using it. Sibling tools are listed but not addressed.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.