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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so safety behavior is fully covered elsewhere. The description adds only that the payload contains metadata and resources; it says nothing about what 'resources' concretely entails, whether the result can be large, or how invalid dataset ids are handled, so the added behavioral value is modest.

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 filler and no repetition of the title. It is efficient, though the brevity shades into under-specification given the undocumented parameter.

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 no output schema, the description does at least name the two return categories (metadata and resources), which is the minimum needed. But for a lookup tool it omits the identifier format, prerequisites, and failure behavior, leaving meaningful gaps.

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 0% for the single required dataset_id, so the description must carry the burden and does not. It never states the id format (numeric, slug, UUID) or where the id comes from (e.g., istanbul_search_datasets), which is the one piece of information an agent needs to invoke this correctly.

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 gives a specific verb (return) and resource (metadata and resources for one IBB dataset), which is far more informative than the title alone. It implicitly differentiates itself from list-style siblings like istanbul_search_datasets and row-extraction siblings like istanbul_query_resource, but it never names them, so the differentiation is left to inference.

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?

There is no explicit when-to-use or when-not-to-use statement and no mention of alternatives. The phrase 'for one IBB dataset' plus the required dataset_id only implies the usage pattern (you already know which dataset you want), leaving the agent to infer that istanbul_search_datasets is the prerequisite when the id is unknown.

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