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

Annotations already declare readOnly/idempotent/openWorld/non-destructive, so the safety profile is covered. The description adds useful method context ('datastore_search, not SQL') and mentions 'guarded filters and limits', but 'guarded' is never explained — no stated cap, error behavior, or cost of broad scans.

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?

Three short lines, purpose front-loaded, with the API reference link serving as a compact pointer to fuller docs. Slightly terse on the one point (limit) that most needs spelling out.

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?

A 3-parameter read tool with no output schema and full annotation coverage — so the bar is modest — but the description omits the return shape of datastore_search (records/fields/total) and the limit ceiling, both of which change how an agent calls it.

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 carries the burden; it does clarify that filter keys must match the resource schema, which is real semantic value. But limit goes undocumented (no default, no max, no behavior when null) and resource_id's sourcing (from get_dataset/istanbul_search_datasets) is left implicit.

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 (IBB CKAN DataStore records) and adds the mechanism ('datastore_search, not SQL'). However, it never distinguishes itself from the near-identical sibling istanbul_datastore_query, leaving the agent to guess which to call.

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?

'Field names come from the resource schema' implies a prerequisite workflow (call istanbul_get_resource_schema first) and 'not SQL' rules out a competing approach. But there is no explicit when-to-use vs the datastore_query sibling or when-not to use this tool at all.

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