get_oss_rules

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 implies a static reference lookup but says nothing about permissions, return shape, caching/staleness, or whether the response is a rule set versus a single rule, leaving an agent with little behavioral grounding.

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?

Two tight sentences with the resource definition front-loaded and the scope enumeration second. No filler, no repetition of the tool name.

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, parameterless reference lookup with no output schema, the description covers what the tool returns at a topical level (the three OSS regimes). It could say more about the form of the returned rules, but nothing critical to invoking it is missing.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond the fact that the lookup is unconditional, which the empty schema already conveys.

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 (Get) plus resource (OSS/IOSS rules) and expands the acronym, then names the three sub-domains (Union, Non-Union, Import OSS). It is clearly distinct from the VAT-rate and e-invoicing siblings, though it never names an alternative directly.

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 'for EU cross-border B2C sales' implies the situation in which this applies, which is useful context, but there is no explicit when-to-use directive, no exclusions, and no routing to or away from siblings such as get_vat_rates or get_reverse_charge_rules.

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