Search Official Arma Reforger Documentation

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

Annotations already provide readOnlyHint=true and openWorldHint=false. The description adds context that the catalog is 'curated' and 'offline', which is useful but does not disclose additional behavioral traits such as authorization needs or result format. It adds some value beyond annotations.

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 short and front-loaded with the key purpose. However, including a bilingual version (German) adds redundancy for an agent likely operating in English. It could be more concise by omitting the German text, but it is still efficient.

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?

The description lacks details about result format, limitations (e.g., only documentation, not code), and parameter usage. Given that there is no output schema and schema coverage is 0%, the description does not sufficiently compensate to make the tool's usage fully clear.

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%, and the description does not explain the 'query' or 'limit' parameters at all. It only describes the catalog being searched. For a search tool, parameters are critical, and the description fails to add meaning beyond the schema's basic definitions.

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?

Description clearly states the tool searches a specific curated, offline catalog of official documentation and samples. It distinguishes itself from siblings like search_workspace or search_local_api by specifying the source (Bohemia Interactive) and nature (curated, offline).

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 implies it should be used for official docs via 'primary Bohemia Interactive documentation and samples', but it does not provide explicit guidance on when to use this versus alternative search tools, nor does it mention when not to use it.

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