Get ILOSTAT indicator metadata

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

Annotations indicate readOnly, openWorld, idempotent, and non-destructive, and the description correctly implies a read-only operation. The description adds useful behavioral details beyond annotations, such as not returning statistical values or codes, and the provenance modes. However, it could have elaborated on the detailed provenance mode's contents.

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 concise at two sentences, front-loads the primary purpose, and uses clear negative statements to set boundaries. Every sentence contributes actionable information.

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?

Given the complex domain and presence of an output schema, the description sufficiently covers the tool's role and usage context. It could mention the 'concise' default more loudly but overall is adequate for a read-only metadata lookup tool.

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 description adds key context by explaining the dataflow parameter's source (from ilo_search_indicators) and the provenance_mode options with defaults. This goes beyond the schema's basic descriptions.

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 the tool provides the structure of an ILOSTAT dataflow, including dimensions, codelists, time dimension, default selection, and data vintage, which clearly distinguishes it from siblings like ilo_get_data and ilo_list_dimension_values. It also explicitly mentions what it does not do.

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 advises using this tool before ilo_get_data to know which filters exist, and also directs users to ilo_list_dimension_values for codes. This provides clear when-to-use guidance and names alternative tools.

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