Find game ids

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restating. The description adds real scope context that annotations cannot: mods' and data packs' ids are included. It stops short of describing result ordering or paging behavior beyond what the schema's cursor/limit notes convey.

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?

Front-loaded with the purpose, then the search semantics, then the routing advice — good ordering with no filler. The registry list is somewhat redundant against the enum but serves as a quick scan of coverage, so it mostly earns its place.

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?

No output schema exists, but the limit description ('0 answers only the total, to count without listing') and nextCursor parameter implicitly convey the return shape and paging. For a read-only lookup tool with fully documented params, this is close to sufficient; an explicit note on returned id format/ordering would complete it.

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 coverage is 100%, so the baseline is 3, but the description adds genuine meaning: 'Search by words: `oak log` finds minecraft:oak_log and minecraft:stripped_oak_log' reveals token/word matching rather than literal-substring matching, which the schema's 'Words every id must hold' only hints at. The registry enumeration reinforces the enum values.

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?

Specific verb+resource ('The exact ids the game knows, from its registries') with an enumerated registry scope. It is clearly distinguished from siblings like search_commands, get_block, and get_recipes.

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?

Explicitly names the six downstream tools (spawn_entity, set_effects, edit_items, set_blocks, locate, world_effect) and the condition 'when you aren't sure of an id'. It also demonstrates the search behavior with a worked example, so when-to-use is unambiguous.

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