Get company by VAT ID

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing — not whether it is a pure read, what happens on an unknown VAT ID (error vs. empty), whether results are cached or scoped to an account, or what the response contains.

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?

It is short, but the brevity is under-specification rather than economy: one echoed identifier earns no informational value and leaves the reader with nothing front-loaded except the name they already had.

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 (one required param, no nested objects, no output schema), so a short description could suffice — but nothing is said about lookup outcome, format expectations for the VAT ID, or failure behavior, leaving critical context entirely absent.

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 vatId is documented in-schema as "VAT / UID number" with a minLength constraint. The description adds nothing beyond that, but per the high-coverage baseline a 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 is "GetCompanyByVatId." — a restatement of the tool name and title with no additional specification. It does not clarify what entity is returned, what the lookup semantics are, or how it differs from siblings such as get_company, get_companies, find_companies, or get_reseller_by_vat_id.

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?

There is no when-to-use guidance, no exclusions, and no mention of any alternative. An agent choosing between get_company_by_vat_id, get_company, get_companies, find_companies, and get_reseller_by_vat_id gets no routing signal at all.

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