Consultar los datos de un recurso (DataStore)

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful context (queries in place rather than downloading) but says nothing about rate limits, whether all resources are DataStore-enabled, or error behavior for non-tabular resources.

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?

A single front-loaded sentence with no wasted words; the core capability and the 'no download' distinction come first. Slightly dense with a parenthetical, but efficient overall.

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 an output schema present, return values need not be described, and all 8 parameters are documented in the schema. The description covers the main capability adequately for a filtered-query tool, though it omits guidance on DataStore availability and sibling routing.

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%, so every parameter (rows, sort, query, filters_json, offset, source, etc.) is already documented in the schema. The description names the same capabilities (full-text query, exact filters, sort, pagination) without adding syntax or format detail beyond what the schema provides, so the baseline 3 applies.

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 (Query) and resource (tabular CKAN resource) plus the mechanism (through the DataStore without downloading it), which clearly separates it from download_resource. However it never names or distinguishes itself from the close sibling preview_resource_data, so sibling differentiation is incomplete.

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?

'Without downloading it' implies the alternative is download_resource, giving implied guidance. But there is no explicit when-to-use / when-not statement and no mention of when preview_resource_data would be preferable, leaving routing to inference.

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