Reads ELSTER inbox messages and optionally downloads each as a PDF, so users can review tax notices and retrieve documents without opening messages individually.
Reads ELSTER inbox messages ("Posteingang"). Optionally downloads each message as PDF.
| Name | Required | Description | Default |
|---|---|---|---|
| maxPages | No | ||
| downloadPdfs | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavioral traits but only states two actions: reading and optionally downloading PDFs. It fails to mention authentication requirements, side effects (e.g., state changes from downloads), pagination behavior, or error handling, which are critical for safe invocation.
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, properly front-loaded with the primary action. However, it could benefit from slightly more structure to separate reading from downloading, though overall it remains 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?
Given no output schema and only two parameters, the description lacks detail on the return format (e.g., message list with metadata), prerequisites, and edge cases. While the tool appears simple, the description omits information needed for reliable invocation.
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 the description must explain parameters. It only hints at 'downloadPdfs' via 'Optionally downloads each message as PDF', but provides no meaning for 'maxPages'. The parameter semantics for half the parameters are entirely unaddressed.
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 specifies the verb 'Reads' and the resource 'ELSTER inbox messages', with an optional action 'downloads each message as PDF'. It differentiates from sibling tools which cover config, sessions, forms, etc., making the purpose unambiguous.
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 (e.g., for specific inbox filtering or batch operations). The description does not mention prerequisites or when not to use it, leaving the agent to infer context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.