List Linked SPARQL Endpoints

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety is clear. The description adds value by detailing the return structure (list with endpoint URL, title, description, conformsTo standard) and source catalog, which goes beyond 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 extremely concise, using a few short sentences to cover purpose, arguments, returns, and usage. The structured format with 'Args:' and 'Returns:' sections, plus a 'Use when' tip, is efficient and easy to parse.

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 no parameters and no output schema, the description provides adequate context: it specifies the source (schema.gov.it catalog), return fields, and usage scenario. It might lack details on pagination or limits, but for a catalog exploration tool, it is sufficiently 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?

The tool has zero parameters, so the description has no need to explain parameters. Schema coverage is 100% (vacuously). The description correctly states 'Args: None', which is sufficient.

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 the tool discovers SPARQL endpoints from the schema.gov.it catalog via dcat:DataService. It uses a specific verb ('Discover') and resource ('SPARQL endpoints'), distinguishing it from sibling tools like list_datasets or list_ontologies.

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 'Use when' section explicitly advises to use the tool when exploring external SPARQL endpoints connected to the Italian PA semantic catalog. While it doesn't mention alternatives or when not to use it, the guidance is clear and context-appropriate.

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