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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety/behavior profile is largely covered. The description adds only the modest caveat 'or extended registry info where available', hinting that data completeness varies by country, but says nothing about auth requirements, latency, or per-country feature gaps.

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?

Front-loaded first sentence with a clean Args block; every element earns its place. The separate 'Returns:' sentence slightly duplicates the opening 'Returns advanced company information' and could be merged.

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 two-parameter read tool with annotations and no output schema, the essential call mechanics are present. However, the sibling-overlap problem (EU vs WW vs IT, start vs advanced) and the country-specific variation in returned data are not addressed, which is the main gap for correct selection.

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 coverage is 0%, so the description carries the full parameter burden and does so: it aliases vatCode to 'VAT code or company registration number' and clarifies country_code as a two-letter code with examples (FR, DE, ES). Only the vatCode format/validation remains unspecified.

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 ('Returns advanced company information for a company in the specified country') and scopes it geographically via the name/title. It does not differentiate itself from the many near-identical siblings, notably get_company_EU_start, get_company_WW_advanced, and get_company_IT_advanced, so the agent cannot tell which variant to pick from the text alone.

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 and no alternatives named, even though the sibling set contains an obvious 'start' versus 'advanced' distinction and multiple geographic variants (EU/IT/WW). The agent is left to infer precedence between them.

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