get_skattekort_resultat

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

No annotations are provided, so the description must carry the full burden. It only says 'Retrieve' (implying read-only) and 'completed order' as a precondition, but does not disclose error behavior for incomplete orders, authentication needs, response format, or any side effects. This is a significant gap for a no-annotation tool.

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 with no filler. Every word earns its place, and it conveys the core purpose and key condition efficiently.

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 one-parameter retrieval tool without output schema, the description covers the essential purpose and a key usage condition. However, it lacks any hint about the result contents, the relationship to sibling tools like order_skattekort (beyond the parameter description), or potential failure scenarios, leaving it minimally adequate.

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 input schema already describes ordreId as 'Order ID from order_skattekort', giving 100% coverage. The description adds no further parameter detail, but since the schema fully documents the parameter, the baseline score of 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 uses a specific verb ('Retrieve') and resource ('skattekort results for a completed order'), clearly distinguishing it from siblings like order_skattekort (ordering) and get_skattekort_ordre_status (status only). The qualifier 'completed order' removes ambiguity about what results are being fetched.

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?

'For a completed order' provides clear context that this should be used only after an order has been finalized, implying the sequence relative to order_skattekort. However, it does not explicitly name alternatives or say when not to use it, so it stops short of full exclusion guidance.

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