declaration_form_versions

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

Annotations already establish that this is a safe, read-only, idempotent lookup. The description adds meaningful behavioral context beyond that: it discloses that results include DUKIntegrator's manifest view, changedRecently over the last 30 days, localOutdated status, and that the endpoint is public with no account needed.

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 is compact and front-loads the core purpose before explaining the derived fields and usage trigger. The parenthetical explanation is dense but each clause adds concrete meaning about the response.

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 input parameters and no output schema, the description carries the burden of explaining what is returned. It names the key response concepts and the practical decision it supports, though it does not describe the overall response shape or any pagination/format details.

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?

This tool has zero parameters, so there is no parameter semantics burden. The description correctly does not discuss inputs, matching the empty schema.

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 states a specific resource and scope: 'ANAF's current version of every declaration form (validator J and PDF P)' as listed by DUKIntegrator's manifest. It also distinguishes the payload by naming the included derived fields, so an agent can tell this apart from related tools like declaration_forms and declaration_form_spec.

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?

It gives a clear usage trigger: 'Check it before building or filing when a rejection mentions the form version.' It does not explicitly compare this against sibling tools such as declaration_forms or declaration_form_spec, so it stops short of full alternative routing guidance.

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