Naviga Archivio BDP

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

Annotations already indicate readOnlyHint=true, so the read-only nature is covered. The description adds the hierarchy path but does not disclose important behaviors like handling of partial parameters, default values, or response format. It provides modest additional context beyond the annotations.

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 a single, efficient sentence with no redundancy. It is front-loaded and to the point, though it may be slightly under-specified given the tool's complexity; still, every word earns its place.

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 7 optional parameters and no output schema, the description is not complete enough to enable correct invocation. It omits details about required parameter combinations (if any), the role of target, the expected output, and how the navigation results are structured.

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?

With 0% schema description coverage, the description partially compensates by naming the hierarchy levels, which map to distretto, ufficio, materia, anno, and mese. However, it does not explain the target or max_results parameters, nor does it clarify how parameters combine, leaving gaps.

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 tool's action ('Naviga la struttura gerarchica') and specific resource (the BDP archive hierarchy with levels Distretto → Ufficio → Materia → Anno → Mese). This is distinct from sibling tools like search and read, making it easy to understand what this tool does.

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 implies usage for browsing the archive hierarchy, but does not explicitly state when to use it over alternatives such as cerca_provvedimenti or leggi_dettaglio_provvedimento. No exclusions or alternative references are provided.

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