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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It offers only 'Generate ... from a NIP or PESEL' with no detail on whether this is a remote lookup, whether it persists anything, error behavior on invalid identifiers, or rate-limit considerations. For a tool with zero annotation coverage, this is a significant gap.

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?

A single, front-loaded sentence with zero wasted words. The action and input are stated immediately and the tax-payment scope is packed in parenthetically.

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?

The single input parameter is fully described, but with no output schema and no annotations, the agent has no idea what the tool returns (the account number? some structured object?) or how invalid input is handled. For a 1-param tool this is tolerable but not complete.

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% (the schema documents 'NIP (10 digits) or PESEL (11 digits)'), so the baseline is 3. The description simply repeats that input is NIP or PESEL, adding no format, validation, or usage nuance beyond what the schema already states.

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?

States a specific verb ('generate') and resource ('individual tax micro-account for PIT/CIT/VAT payments') with the input source (NIP or PESEL). The verb contrasts with the sibling 'sprawdz_*' check tools, but the differentiation is implicit rather than explicit, and the term 'mikrorachunek' isn't explained for agents unfamiliar with Polish tax concepts.

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 context is implied (use when you have a NIP/PESEL and need a micro-account for tax payments), but the description names no alternatives and gives no exclusions or when-not-to-use conditions. It doesn't clarify how this relates to siblings like sprawdz_rachunek or sprawdz_nip.

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