Elenca archivi Domustudio configurati

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint. The description adds meaningful context beyond them: the backend exposes only three GET endpoints, Domustudio remains the system of record, and corrections must be made by an operator. It does not frame this limitation in terms of what the agent should do instead.

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?

Front-loads the purpose, then the operational rule, then the return shape. It is somewhat long and the return-value block duplicates the output schema, but each section is purposeful and no sentence is wasted.

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?

Output schema exists, so explaining return values is optional but harmless. With rich annotations, an empty schema, and clear scoping rules, an agent has everything needed to call this tool correctly and to understand its relationship to the siblings.

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?

Zero parameters, so the baseline is 4. The description correctly states 'Nessun parametro,' confirming the empty schema, and adds the cross-tool rule about the 'archivio' parameter expected by sibling tools.

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?

States a specific verb and resource ('Elenca i nomi degli archivi Domustudio configurati') and clearly distinguishes itself from siblings by explaining that it is the discovery tool for the archive name that every other tool requires. An agent can identify its role without opening any schema.

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?

Explains the selection logic explicitly: one API key maps to one archive, every other tool takes an 'archivio' parameter, and that parameter may be omitted when only one archive exists. This is clear context, though it stops short of an explicit when-not-to-use or a named alternative.

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