check_saved_search

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

The description discloses that the tool updates last_checked_at and last_finnkodes, which are side effects beyond the schema. It also explains the first-call behavior. Since no annotations are provided, the description fully carries the transparency burden.

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 extremely concise: two sentences and a list of side effects. Every line serves a purpose, and the main verb 'Run' leads the text. No superfluous content.

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?

Given the tool has an output schema (not shown but known), the description adequately covers the behavior and side effects. However, it could explain the term 'last_finnkodes' and provide more context about the input format, but it remains sufficient for a simple tool.

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?

Only one parameter 'name' exists, and the description does not mention it at all. With schema coverage at 0%, the description should add meaning (e.g., what names are valid or how to construct them), but it fails to do so.

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 action: run a saved search and return new listings. It specifies the resource (saved search) and the unique behavior (only new results). This distinguishes it from siblings like search_finn or list_saved_searches.

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 explains that on the first call all results are new, implying subsequent calls yield only new changes. However, it does not explicitly state when to use this tool versus alternatives like search_finn, nor does it list preconditions or exclusions.

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