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

It explicitly states a behavioral trait: the `days` parameter has a default value of 30. Since annotations provide safety hints (`readOnlyHint`), this description successfully adds helpful, non-obvious operational context regarding default behavior.

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 definition is extremely concise and front-loads the most important information (what it filters by and the default time window) in a single, readable sentence.

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?

It is comprehensive for a filtering tool, defining the time scope, the default behavior, and the sorting order of results ('soonest first'). It provides all the logical constraints needed to utilize the tool correctly.

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?

Since schema description coverage is 100%, the parameter semantics are highly valued when the description adds specific functional meaning. Explaining that the results are ordered 'soonest first' provides critical context on expected output structure and prioritization.

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 tool is clearly designed to identify 'open calls closing soon,' which distinguishes it from general call listings or order searches in the sibling tools. The title ('Bandi in scadenza') and description provide immediate context.

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 does not advise the agent on when to use this specific tool versus a broader search function (like using `search_remote_jobs` for all jobs). It states what the tool *does*, not how it fits into a decision tree of available tools.

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