Retrieve Polish tax documents by entering a signature or prefix. Get verifiable citations with URLs directly from the EUREKA system.
Skrot: szuka dokumentu po sygnaturze (pelnej lub prefiksie). Odpowiednik search z parametrem signature. Bledy: missing_arg (brak signature), upstream_error.
| Name | Required | Description | Default |
|---|---|---|---|
| signature | Yes | Sygnatura, np. '0112-KDIL3.4012.367.2026.2.AK' albo prefiks '0114-KDIP2'. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds that it is a shortcut and lists possible errors, which provides some additional context.
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?
Very concise two-sentence description that is front-loaded with purpose and includes equivalent tool reference and error types.
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 tool with one parameter and no output schema, description covers purpose, usage, and errors adequately.
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 100%, so baseline 3. Description adds meaning by explaining 'full or prefix' and providing an example parameter value.
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?
Clearly states the tool searches for documents by signature (full or prefix). Distinguishes from sibling 'search' by being a shortcut with signature parameter.
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?
Explicitly says it is equivalent to search with signature parameter, providing clear use context. Mentions error types but does not explicitly state when not to use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.