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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds one useful piece of context — that the payload includes the router and its conditions — but says nothing about auth needs or payload shape beyond that.

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 with no filler — the resource, the required input, and the notable return content are all packed in efficiently. Not padded, though also not especially well structured for scanning.

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?

There is no output schema, so the description must speak to returns, and it does ('tutti i dati ... compreso il router con le sue condizioni'). For a simple one-parameter read lookup with full read-only annotations, this is close to complete; only slug provenance and error behaviour are unaddressed.

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?

Schema coverage is 0%, so the description carries the burden for the single 'slug' parameter. 'dato il suo slug' tells the agent the identifier is an offer slug, which is helpful, but gives no format, source, or validity guidance.

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 names the resource and scope precisely ('tutti i dati di una singola offerta'), and the singular 'singola' implicitly distinguishes it from the sibling elenco_offerte (list of offers). The retrieval verb is implied rather than stated, so it falls just short of a 5.

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?

There is no explicit when-to-use guidance, no prerequisites (e.g. where the slug comes from, whether the offer must be active), and no named alternative. The only hint is the singular/plural contrast with elenco_offerte, which the agent must infer.

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