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

No annotations are provided, so the description carries the behavior burden. 'Hent stamdata' communicates a read-only retrieval of registered data, but nothing is said about authentication, rate limits, caching, or what happens with an invalid/unknown CVR number. Adequate but not rich for a tool with zero annotation coverage.

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 compact sentences with zero filler: the scope first, then the input requirement. Every clause earns its place.

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, the description usefully enumerates the returned data domains (name, status, address, industry, legal form, owners, management, employees), which compensates well for the missing return specification. Minor gaps remain around error/empty-result behavior, but an agent has enough to call it correctly.

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% with a single fully documented parameter (pattern ^\d{8}$ plus example '43269070'). The description's restatement of the 8-digit CVR number adds no format or syntax detail beyond the schema, so baseline 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 (hent) and resource (stamdata for a Danish virksomhed from CVR-registret) and enumerates the data domains returned (navn, status, adresse, branche, virksomhedsform, ejere, ledelse, ansatte). It does not explicitly distinguish itself from the siblings search_companies or get_company_financials, so it stops short of a 5.

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?

Usage is implied rather than stated: 'Input er det 8-cifrede CVR-nummer' tells the agent this tool applies when a CVR number is already known, implicitly contrasting with search_companies. There is no explicit when-to-use/when-not statement or named alternative, which keeps it at the implied-usage level.

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