osint_iban_validator

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

No annotations provided, so description carries full burden. It discloses the validation, extraction, and formatting behaviors, but does not mention side effects, external dependencies, or read-only nature. Adequate but not thorough.

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?

Concise at three sentences, but the first sentence is redundant ('Menu ID: iban_validator. IBAN Validator.'). Front-loaded purpose is good, and reference to describe_tool is helpful.

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 one-parameter tool, the description covers purpose and basic behavior. However, no output schema and reliance on describe_tool for full guidance leaves gaps. Could be more complete given sibling tools.

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?

Only one parameter 'iban' with 0% schema description coverage. The description confirms it is the IBAN number, but lacks expected format, length, or examples. Adds basic meaning but not detailed semantics.

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 the tool validates IBANs, checks format, verifies check digits, extracts bank information, and formats them. This specific verb+resource combination distinguishes it from siblings like osint_bic_swift_validate.

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 implies use when IBAN validation is needed but does not explicitly compare with alternatives or state when not to use. No guidance on prerequisites or exclusions.

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