rce_linked_data_select

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

Annotations already declare readOnlyHint and openWorldHint. The description adds value by explicitly stating that only SELECT queries are permitted and that LIMIT is capped, which are behavioral constraints not fully covered by 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 with two sentences that are front-loaded, containing no wasted words. Every sentence adds essential information.

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 complexity of a SPARQL query tool and the absence of an output schema, the description is adequate but lacks details about the return format (e.g., SPARQL JSON results). This gap may hinder an agent from correctly parsing the response.

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 must compensate. It only vaguely mentions 'SPARQL SELECT query' and 'LIMIT is capped', leaving the 'query' parameter unexplained in terms of format, syntax, or expected values. This is insufficient for an agent to correctly formulate a query.

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 executes a read-only SPARQL SELECT query on RCE cultural heritage linked data, specifying allowed query type and constraint (LIMIT capped). This distinguishes it from the sibling 'bag_linked_data_select' tool, which targets a different dataset.

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 implies usage for querying RCE linked data and notes that only SELECT queries are allowed, but it does not explicitly provide when-to-use or when-not-to-use guidance compared to alternatives like bag_linked_data_select or other search tools.

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