bfs_list_themes

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint. The description adds beyond this: it details the return structure (theme codes, names, dataset counts) and error handling (error and hint fields). This is valuable behavioral context.

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-structured with a clear first sentence capturing the main purpose, followed by details on return and parameter. It is concise without being terse, though the second paragraph on returns could be slightly tightened.

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 list tool with one parameter, the description is complete: it explains the output format, error handling, and connection to a sibling tool. No pagination or limits are needed since it returns all 21 themes.

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?

The input schema already describes the lang parameter with a description and pattern. The tool description only repeats 'Language code: de, fr, it, en' in the args section, adding no new meaning. Schema description coverage is 0% per context, so 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 clearly states it lists all 21 BFS statistical themes with codes and dataset counts, and explicitly mentions it returns the complete taxonomy. It also distinguishes itself from sibling bfs_list_tables_by_theme by noting the theme codes are used to filter datasets.

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 clear context: use this tool to get the complete taxonomy, and the theme codes are used for filtering with bfs_list_tables_by_theme. It specifies the language parameter. While it lacks explicit 'when not to use' guidance, the context is sufficient.

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