ms_geology_enumerate_surface_terminations

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

With no annotations provided, the description carries the full burden. It discloses that the tool does not select or repair a termination, but it does not explain side effects, whether files are created, whether confirmation_token is needed, or how dry_run behaves. The presence of task-related parameters (idempotency_key, timeout_seconds) suggests a possibly long-running or irreversible operation, but the description remains silent.

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 a single, compact sentence with no fluff. It front-loads the verb and resource, making it easy to scan. However, its brevity is detrimental to semantic completeness, but that is a completeness issue, not a conciseness one.

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?

Despite the tool having 16 parameters, 11 required, and a non-trivial domain (surface termination enumeration), the description gives no context on how to prepare inputs, what the output will be, or how it fits in a larger workflow. The output schema exists but is not shown, and the one-sentence description is insufficient for an agent to invoke this tool correctly.

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 has 16 parameters with no descriptions (0% coverage), and the description does not explain any of them. Required parameters like input_bulk_structure, top_positions, and output_slot are completely undefined. The description provides zero help in filling the arguments.

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 uses a specific verb ('Enumerate') and resource ('nonproduction surface candidates'), and clarifies that it does not select or repair a termination, which helps distinguish it from a selection/repair step. However, it does not name a sibling tool or explicitly state what is produced, leaving some ambiguity about the exact output.

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?

No guidance is given on when to use this tool versus alternatives like ms_geology_build_periodic_slab_cell. The phrase 'without selecting or repairing' implies a pre-selection step, but there is no explicit when-to-use or exclusion. Prerequisites are not mentioned.

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