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

No annotations are provided, so the description carries the full burden. It usefully discloses a cost model ('10 point per returned record') and enumerates the returned fields, but says nothing about behavior when the registration number is invalid or not found, nor about rate limits or idempotency of repeated calls.

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: verb, source registry, accepted identifier, then a colon-delimited field list and the cost. No filler, nothing buried.

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?

With no output schema and no annotations, the description compensates well by enumerating the returned fields (name, status, address, tax/VAT, business units) and the per-record cost. It is only slightly incomplete on failure behavior and any authentication requirements.

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% and the single parameter is already documented in the schema, including the matična številka wording and a sample value. The description restates the same dual-input semantics (number or registry link) without adding format details, so the baseline of 3 applies.

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 and resource ('Get one company from the Slovenia registry (AJPES PRS)') scoped to a single-record lookup, which implicitly separates it from the sibling run_si_companies_search. It stops short of naming that sibling explicitly, so the differentiation is inferred rather than stated.

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 phrase 'Get ONE company ... by registration number or registry link' implies usage as an identifier-based lookup rather than a discovery tool, but there is no explicit when-to-use/when-not guidance and no named alternative to run_si_companies_search.

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