get_inntekt_for_year

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does disclose a key behavior by noting 'Aggregates monthly data', which indicates the tool combines monthly income data. However, it lacks details on output format, required permissions, or error handling, so transparency is only partially addressed.

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?

The description consists of two concise sentences, with the main purpose front-loaded in the first sentence and a valuable behavioral detail in the second. No redundant or unnecessary information is present.

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 get tool with well-documented parameters, the description covers the core functionality and aggregation behavior. However, it does not describe the return value format or explicitly differentiate from sibling tools like get_inntekt, so it is not fully complete for an agent without prior context.

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 provides descriptions for all three parameters (100% coverage), so the schema already handles parameter semantics. The description adds minimal extra meaning beyond referring to 'a given year', which aligns with the inntektsaar parameter. Thus, a 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 clearly states the tool retrieves all income for a person across all 12 months of a given year, using the specific verb 'Get' and resource 'income for a person', and the phrase 'Aggregates monthly data' distinguishes it from a simple per-month retrieval.

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 description provides no guidance on when to use this tool versus alternatives like get_inntekt, nor does it mention exclusions or preferred contexts. It only states what the tool does, not when to choose it.

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