check_nip_bank_account

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

No annotations are provided, so the description must carry the full behavioral burden. The verb 'verify' strongly implies a read-only operation, but the description does not explicitly state there are no side effects, permissions required, or other relevant behavioral details. It is not misleading, but minimal.

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 clear sentence with no redundant words or repetition. It earns its place by stating exactly what the tool does.

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 tool is simple, with all parameters documented in the schema. The description fully captures the action and implies a boolean result. It lacks explicit mention of return format or any edge cases, but given the simplicity, it is nearly 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 description coverage is 100%, with each parameter (nip, date, bankAccount) already documented with types, patterns, and descriptions. The description adds no additional parameter-level semantics beyond reminding that the bank account is being verified against a NIP. Baseline 3 is appropriate.

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 uses a specific verb ('verify') and resource ('bank account assigned to a specific NIP'), clearly distinguishing it from the sibling tool 'check_nip' which likely just checks NIP validity. The purpose is unambiguous and actionable.

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 clearly states the tool's context (verifying bank account assignment to a NIP) but does not explicitly mention alternatives or exclusions. The sibling tool 'check_nip' provides implicit contrast, but no direct guidance is given in the description.

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