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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered. The description adds useful behavioral context: it returns codes, names, and descriptions; it requires a dataflow code; it notes no auth is required; and it cites the source (kidb.adb.org). It doesn't describe pagination or response size, but for a read-only listing tool with strong annotations, the added context is solid.

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 compact and front-loaded: the first sentence states the core action and output. The example and typical codes are useful, not filler. The source and auth note are relevant. Every sentence earns its place, and the length is appropriate for the tool's complexity.

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 single-parameter read-only listing tool with a full output schema, the description is complete. It covers what the tool does, what it returns, how to use the results, example inputs, and source/auth context. The output schema handles return-value details, so nothing an agent needs to call it correctly is missing.

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 the schema already documents the single 'dataflow' parameter well, including examples and a pointer to adbkidb.dataflows_list. The description adds value by explaining what the returned codes are for (use with adbkidb.data) and giving typical dataflow codes, which helps the agent pick a valid value. With only one parameter and full schema coverage, the description's extra examples push it above the baseline 3.

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 states a specific verb ('List'), a specific resource ('all available indicators within an ADB KIDB dataflow'), and the output content ('indicator codes, names, and descriptions'). It also provides concrete examples (EO_NA returns GDP, GVA, investment, savings indicators with codes like NGDP_XDC and NGDP_RPCH), which makes the tool's purpose unmistakable. It distinguishes itself from sibling tools like adbkidb.data.query and adbkidb.explore.dataflows by explicitly saying to use returned codes with adbkidb.data to query observations.

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 when to use this tool: to list indicators for a given topic category, and it tells the agent to use the returned codes with adbkidb.data for actual time-series observations. It also provides typical dataflow codes (PPL_POP, EO_NA, MFP_XR, GLB_ET, ENV_CC) and points to adbkidb.dataflows_list to discover all 62 codes. This is clear routing guidance relative to siblings.

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