bag_linked_data_select

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds that the tool is read-only and enforces SELECT-only queries with a LIMIT cap, which aligns with and extends the annotations. No contradictions; the added detail on query restrictions is valuable.

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 sentence that conveys all key information without extraneous words. It is front-loaded with the main action and constraints, making it highly efficient.

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 has two parameters and no output schema, the description covers the essential purpose and constraints. However, it omits details on return format, error handling, and query construction conventions (e.g., required prefixes). For a SPARQL query tool, this information is important for proper usage, leaving the description somewhat incomplete.

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% as no parameter descriptions are provided in the schema. The description adds meaning by stating the 'query' parameter is a SPARQL SELECT query and the 'limit' parameter is capped. However, it does not explain the required query format (e.g., prefixes, endpoint specifics), so it provides moderate value beyond the raw 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 executes a read-only SPARQL SELECT query on Kadaster BAG linked data (buildings and addresses), and specifies that only SELECT queries are allowed with a capped LIMIT. This uniquely identifies the tool's function and distinguishes it from sibling tools like bag_address_detail or rce_linked_data_select.

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 that only SELECT queries are allowed and LIMIT is capped, providing clear constraints. However, it does not explicitly compare to sibling tools or advise when to use this over alternatives like bag_lookup_address. The context is clear but lacks explicit exclusions.

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