isir_udalosti

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

No annotations are provided, so the description must carry the behavioral burden. It mentions that 'hledat' is case-insensitive and diacritics-insensitive via normalization, and that 'poslednich=N' returns the latest N events. However, it omits other behavioral aspects like whether 'obnovit' forces a refresh, pagination, rate limits, or authentication requirements. Output schema exists but is not referenced.

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 compact and front-loaded with the tool's purpose and key parameter explanations. However, the inclusion of '(záznamů)' and long phrasing about document types could be tightened slightly.

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 5 parameters, no annotations, 0% schema description coverage, and an output schema, the description is minimally adequate. It explains some parameters but misses others (rizeni, obnovit) and does not leverage the output schema. More detail on parameter usage and behavioral traits is needed for full completeness.

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 0%, so the description must compensate. It explains 'oddil' values (A/B/C/D/P), 'poslednich' as returning latest N, and 'hledat' as text filtering with normalization. But it does not describe 'rizeni' (required) or 'obnovit' (boolean refresh?), leaving two parameters undocumented.

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 it returns a list of events (records) for one section of proceedings, including document IDs. It distinguishes from siblings like isir_tok_udalosti by specifying 'jednoho oddílu řízení' and from isir_dokumenty by focusing on events rather than documents.

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 the 'oddil', 'poslednich', and 'hledat' parameters, implying when to use them. However, it does not explicitly state when to use this tool versus alternatives like isir_tok_udalosti or isir_detail_rizeni, nor does it mention prerequisites or exclusions.

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