Ottieni Distretti Giudiziari

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

Annotations already declare readOnlyHint and idempotentHint, so the agent knows it's a safe read operation. The description adds valuable context by stating the data is 'live, non hardcoded', which informs the agent that results are dynamically fetched and not a static list. This goes 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, concise sentence that immediately states the tool's action and resource. Every word earns its place; it is front-loaded with the purpose and includes the key behavioral note about live data.

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 simple, zero-parameter tool with an output schema and safety annotations, the description is sufficient. It clearly communicates what the tool does, the source of the data, and the live nature, leaving no critical gaps.

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?

The input schema is empty with zero parameters, so the baseline is 4. The description naturally does not add parameter details since there are none, and it correctly implies no inputs are required.

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 verb 'estrae' (extracts) and the resource 'distretti giudiziari' (judicial districts), and further specifies the source as the BDP search select. This distinctively identifies the tool's purpose and differentiates it from sibling tools like ottieni_materie.

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 provides context (it's for the BDP search select) and notes that data is live rather than hardcoded, implying it is the appropriate tool for fetching current district options. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention any exclusions.

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