fedlex_get_upcoming_changes

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds that it only considers future dates (dateEntryInForce > heute) and the configurable time window via days_ahead. This goes beyond annotations with no contradictions.

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 short and front-loaded with the primary action. XML tags structure the additional context effectively. A minor deduction for redundancy (the core sentence repeats the title), but overall concise.

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?

The tool has an output schema, which reduces the need to describe return values. However, the description lacks coverage of two parameters (limit, language) and does not explain behavior at limits. Adequate for a simple retrieval tool but not fully comprehensive.

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 0%, yet the description only explains days_ahead (via example and note). The limit and language parameters are not described at all, leaving the agent uncertain about their purpose. The description partially compensates for one parameter out of three.

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 it retrieves upcoming changes to laws ('Ruft Erlasse ab, die in den nächsten N Tagen in Kraft treten'), with a specific verb, resource, and scope (future effective dates). This distinguishes it from sibling tools like fedlex_search_laws or fedlex_get_law_by_sr.

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 <use_case> tag provides explicit guidance for proactive legal monitoring. The <important_notes> ensures only future dates are considered and the window size is constrained. However, it does not mention when not to use this tool or suggest alternative tools.

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