Preview Distribution

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

Annotations already indicate read-only, idempotent, non-destructive. The description adds significant behavioral details: it downloads and previews data, returns 10-15 rows, auto-detects CSV/JSON formats, and has a 10-second timeout. No contradictions with 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 well-structured: a concise purpose sentence, followed by usage context, then clearly labeled sections for Args, Returns, Supported formats, and Timeout. No redundant information; every sentence adds value.

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?

Given the tool's simplicity (one parameter, no output schema, rich annotations), the description covers purpose, usage context, parameter details, return format, supported formats, and timeout. The note about semantic assets adds domain-specific completeness. No gaps are apparent.

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 100% (one param with description). The description adds value by specifying the accepted formats (CSV or JSON) and that format is auto-detected, which goes beyond the schema's generic description. This benefits the agent beyond the baseline of 3 for high coverage.

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 first sentence clearly states the action (Download and preview) and the resource (distribution file). The phrase 'most useful after you already identified a concrete distribution URL' distinguishes it from sibling tools like explore_dataset or inspect_concept, which deal with broader resources. The domain-specific note about semantic assets further clarifies its niche.

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 explicitly states when to use: 'most useful after you already identified a concrete distribution URL.' It provides context about schema.gov.it and distributions belonging to semantic assets. However, it does not explicitly exclude alternative tools or mention when not to use it, so it lacks exclusions.

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