scadenze

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

With no annotations, the description carries the full behavioral burden. It usefully discloses inclusion/exclusion criteria ('non ancora eseguite', 'già scadute oppure in scadenza entro N giorni'), but omits read-only status, permissions, pagination, sorting, and default horizon 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?

It is a single front-loaded sentence with no wasted text. It is concise and well-structured for the purpose, though it could be slightly richer without becoming verbose.

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 query tool with three optional parameters, no annotations, and no output schema, the description should clarify the result shape and operational behavior. It only gives the filtering scope, leaving return values, sorting, and optional filter interactions unspecified.

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 100%, so the schema already documents tipo, reparto, and entro_giorni thoroughly. The description only echoes the N-day horizon and adds no meaning beyond the schema, making the baseline 3 appropriate.

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 names the resource ('attività programmate') and the exact subset it returns: not yet executed, already overdue, or due within N days. It is clear, but it does not explicitly distinguish itself from sibling tools such as report_conformita or cerca_apparecchi.

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?

There is no explicit when-to-use statement, no alternatives, and no exclusions. The deadline scope implies a use case, but an agent is left to infer when to choose this over sibling tools.

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