Ottieni Materie Disponibili

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

The annotations already declare readOnlyHint and idempotentHint, indicating a safe, non-mutating operation. The description adds useful behavioral context: 'live, non hardcoded' means the data is dynamically extracted from the actual select, not from a static list. This gives the agent insight into the data source and freshness 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, front-loaded sentence that clearly states the action and resource: 'Estrae le materie disponibili dal select della ricerca BDP'. There is no filler or redundant information. It is appropriately sized for the tool's simplicity.

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?

The tool has no parameters, read-only/idempotent annotations, and an output schema exists, so return values are covered. The description explains the core function and adds the 'live' qualifier. For a simple retrieval tool, this is sufficiently complete, though it does not describe exact usage context relative to the search process.

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?

This tool has zero parameters, so the input schema is fully covered by default. The description correctly does not need to explain parameter semantics. Per the baseline for 0 params, a score of 4 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 uses the specific verb 'Estrae' (extracts) with a clear resource: 'le materie disponibili dal select della ricerca BDP' (available subjects from the BDP search select). It distinguishes itself from siblings like 'ottieni_distretti' by indicating it returns subject data. The additional 'live, non hardcoded' further clarifies the data source.

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 retrieving the subjects available in the BDP search form, but does not explicitly state when to use this tool versus alternatives like 'ottieni_distretti' or 'ottieni_timeline'. No exclusions or conditions are mentioned. The context is clear, but there is no explicit guidance on alternatives.

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