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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the bar for behavioral disclosure is lower. The description adds real behavioral detail beyond annotations: hierarchical codelists are shown one level at a time with expand, flat codelists use offset pagination, and debug only populates when telemetry is enabled. No contradictions with annotations are present.

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 well organized into purpose, usage context, workflow, and args, with no filler. Every sentence adds useful information, and the most important scoping statement is front-loaded.

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, the description does not need to explain return values. It covers when to use the tool, the hierarchical/flat distinction, pagination, drill-down behavior, and all parameter semantics. For a 6-parameter tool, no critical calling context 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 0%, so the description carries the full burden for parameter meaning. It provides examples for agency_id, dataflow_id, and dimension_id, and explains expand and offset semantics precisely. The debug parameter also gets clarity despite having no schema description.

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: 'Browse the full available code list of ONE dimension, one level or page at a time.' It distinguishes itself from siblings by referencing the workflow (discover -> inspect -> browse_dimension_codes -> build_url) and the condition under which it is used (when inspect shows more codes than it can display). This clearly separates it from inspect, fetch, and build_url.

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?

It explicitly says 'Use this when inspect shows a dimension with more codes than it can display' and distinguishes hierarchical versus flat codelist behavior with expand/offset. It also provides a common workflow, which is clear context, though it does not explicitly enumerate exclusions like 'do not use fetch here'.

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