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

With no annotations, the description carries the behavioral disclosure burden. It does add useful information such as support for pagination and a dd/mm/yyyy date format, but it does not mention result limits, default page, ordering, or the shape of the returned events.

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 only two sentences and front-loads the core purpose before summarizing the filter families and pagination. Every clause adds useful selection or invocation information; there is no filler.

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 tool with eight optional parameters, the fully documented schema plus this concise overview is mostly complete: the agent knows what the tool does, which filters exist, and that pagination is supported. It would be more complete with an explicit note about the result structure, but that is not a critical gap for invoking it 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?

Schema description coverage is 100%, so the schema already documents all eight parameters. The description largely restates the filter types and enum categories without adding deeper parameter-level semantics, so the baseline score of 3 is 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 opens with a specific action and resource: 'Cerca esdeveniments a l'agenda de surtdecasa.cat' and then enumerates the filter dimensions. It is clearly a search tool for agenda events, but it does not explicitly differentiate itself from siblings like cartellera or detall_esdeveniment.

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 guidance about when to choose this tool instead of cartellera or detall_esdeveniment, and no explicit exclusions or 'use this when' conditions. The text explains what the tool can filter by, but not when it is the right choice among siblings.

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