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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safe-read profile is covered. The description adds useful behavior context beyond annotations: exact number of dataflows, no auth required, open-data source, and the hierarchical structure of topic groups. It does not elaborate on search behavior or edge cases, but the output schema and optional search parameter in the input schema reduce the need for that.

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 front-loaded with the core purpose and remains reasonably compact given the amount of useful context. The list of category abbreviations is somewhat long but earns its place by giving an agent concrete known codes. A small improvement would be trimming the source line or moving it to the end, though it is already informative.

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?

For a simple, one-optional-parameter list tool with an output schema and strong annotations, the description is mostly complete: it states scope, content, downstream usage, and auth status. However, the incorrect downstream tool names ('adbkidb.indicators' and 'adbkidb.data') are a real completeness gap—an agent following them may fail to locate the actual sibling tools. Correcting those references would make the description fully reliable.

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% and the search parameter is already well described in the schema with examples and the 'leave empty to list all' behavior. The description itself adds almost no parameter-level meaning, so the baseline of 3 applies. There is no contradiction or gap requiring the description to compensate.

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 opens with a specific verb and resource: 'List the 62 available dataflow categories in the ADB Key Indicators Database (KIDB).' It clearly distinguishes this from sibling exploration tools by framing dataflows as the first step before indicators and data, and it enumerates the topic groups. The scope (62 categories, 50 Asia-Pacific economies) makes the tool's purpose unambiguous.

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 gives a downstream workflow ('Use the returned code with adbkidb.indicators to discover indicator codes, then adbkidb.data to fetch actual values'), which is helpful context, but it does not explicitly say when to choose this over adbkidb.explore.economies or adbkidb.explore.indicators. It also references 'adbkidb.indicators' and 'adbkidb.data' while the actual sibling tools are 'adbkidb.explore.indicators' and 'adbkidb.data.query', which could misroute an agent.

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