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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only discloses that parsing is done offline; it does not mention whether the tool validates, what it returns for malformed input, or how bank/country/branch components are represented.

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 very short, but it repeats 'SWIFT/BIC' and the colon-heavy structure makes it feel terse rather than deliberately concise. It conveys the core idea in one line but could be clearer with slightly more structure.

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 single-parameter tool with no annotations, the description leaves important context unexplained: the exact form of the input, what the output contains, and behavior for invalid codes. The output schema may help, but the description itself is too thin to fully enable correct 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 description coverage is 0% and the only parameter 'q' has no description. The tool name and description imply that 'q' is the SWIFT/BIC code to parse, but no explicit definition, format, or example is provided.

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 states a clear verb ('Parse') and resource ('SWIFT/BIC'), and specifies the outcome ('bank/country/branch'). It is easily distinguishable from the many sibling format/parsing tools because the resource is named explicitly.

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 given on when to use this tool over alternatives or when not to use it. The parenthetical '(offline)' hints at an operational trait but does not explain a selection context or name any sibling alternative.

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