List the most recent amendments across all tracked UK provisions. Useful for answering 'what changed in UK employment law recently?'
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max results (default 50) | |
| since | No | ISO date, e.g. '2026-01-01' |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It signals a safe list operation via 'List' and the read-only nature, but does not mention pagination, side effects, auth requirements, or what 'tracked' means. It is adequate but does not go beyond the obvious.
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 sentences with no wasted words; the primary action is stated first, and the example query is a short useful illustration. It is easy to scan and directly informative.
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 two-parameter read tool with full schema coverage, the description is mostly complete. However, there is no output schema and the description does not indicate the result shape or ordering guarantee beyond 'most recent', so the agent still has some leftover ambiguity about what will be returned.
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?
Input schema covers both parameters at 100% with clear descriptions, so the baseline is 3. The description does not add depth about how 'since' filters or how 'limit' behaves beyond what the schema already states, so it neither deducts nor enhances.
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?
Description uses a specific verb ('List') and precise scope ('most recent amendments across all tracked UK provisions'). It also gives an example user question, making the tool's purpose immediately clear and distinguishable from siblings like get_most_amended or get_provision_history.
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 tool is tied to a concrete use case ('what changed in UK employment law recently?'), which gives clear context. It does not explicitly mention siblings or when not to use it, but the all-provisions scope is sufficiently explicit for an agent to route correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.