bari.tours

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

With no annotations, the description carries the full burden. It usefully discloses the return content and provenance ("short verified answer, sources and last check date"), which is meaningful behavioral context, but it does not mention error behavior, data freshness mechanics beyond the check date, or any access constraints.

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 with examples in parentheses and no wasted text. Every clause contributes to scope, examples, or expected return content.

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 two-parameter lookup with no output schema, the description covers the resource, examples, expected return content, and data provenance. It is nearly complete, with only minor gaps around the language parameter and failure behavior.

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 description coverage is 50%: the name parameter is only described as "Place name or key," but the description adds useful examples ("Matera", "Polignano a Mare"). The language parameter is not mentioned at all in the description, though its enum values (it/en) and default are self-explanatory in the schema.

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 it returns facts about a single destination near Bari, with examples like "Matera" and "Polignano a Mare" and a concrete scope (car/train access, verified answer, sources, check date). It implicitly distinguishes itself from the sibling list tool by focusing on one destination, but does not explicitly name that sibling.

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?

Usage is implied by "Facts about one destination near Bari" and the examples, so an agent can infer when to use it. However, it never explicitly contrasts with list_day_trips_from_bari or states when not to use this tool, leaving routing guidance to inference.

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

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

No annotations are provided, so the description carries the full burden. It usefully discloses the return fields and attributes the data to the independent guide bari.tours, which implies a curated read-only dataset with no auth, but it never states ordering, result counts, or pagination behavior.

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?

One front-loaded sentence with no filler; the parenthetical region and the source attribution both aid disambiguation rather than padding. Slightly dense at the end but nothing that fails to earn its place.

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?

With four optional filters, no annotations and no output schema, the description covers what the tool returns, where the data comes from, and that filtering is optional. Only the absence of any note on result volume or the get_destination relationship keeps it from being fully complete.

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 description coverage is 100% and each filter is fully documented in the schema, so the baseline is 3. The description adds only 'Optional filters', which is largely redundant with the zero required parameters already declared.

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 ('List day-trip destinations from Bari') and goes further by naming the payload fields (driving time, distance, train line) and the data source. It does not explicitly distinguish itself from the sibling get_destination, so it falls 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?

The only guidance is the trailing phrase 'Optional filters', which hints the tool can be called with no arguments. There is no statement of when to use this list tool versus get_destination, no exclusions, and no note on whether results are exhaustive or capped.

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