driftguard_get_recipe

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

With no annotations at all, the description carries the full burden. It does disclose the filtering behavior (only successful and essential commands, cleaned and ordered), which is real behavioral content beyond the name, but it never states whether the operation is read-only, which environment or snapshot scope it applies to, or what form the output takes.

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?

A single front-loaded sentence that names the artifact first and qualifies it second, with no filler. It is dense but earns its words; only the mixed Italian/English vocabulary against English sibling names adds friction.

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 zero-parameter tool with no output schema and no annotations, the description should clarify what the returned artifact looks like and what scope it covers. It describes the content of the extract but leaves the scope (which environment or snapshot, current state vs. history) and the delivery format unstated.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. The baseline of 4 applies; the description correctly implies no arguments are needed.

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 ('Genera') and a named resource ('Reproducibility Blueprint'), then defines that resource as a filtered extract of only successful and essential commands. This is enough to tell an agent it is not the same as driftguard_list_snapshots or driftguard_create_snapshot, though no sibling is named explicitly.

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 phrase 'per riprodurre lo stato dell'ambiente' hints at the goal, but there is no explicit when-to-use rule, no when-not-to-use, and no reference to any of the seven sibling tools such as driftguard_rollback or driftguard_list_snapshots. An agent must infer that this is the read-only export step rather than the rollback step.

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