get_registry_info

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

With no annotations at all, the description carries the full burden of behavioral disclosure. It states 'Get information,' which reasonably implies a read-only operation, but it does not disclose what shape the information takes, how invalid registryType values are handled, or any error/edge-case behavior.

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?

A single, front-loaded sentence with no filler. It states the action and the resource, then gives clarifying examples. Efficient, though it could have used the saved space for behavioral detail.

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 one-parameter query tool, the description plus schema cover the basics: what it does and what the parameter means. However, there is no output schema and no description of the return value, so an agent cannot predict what kind of 'information' will be returned or how to interpret 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 description coverage is 100% — the registryType parameter is already documented with examples (Block, Item, EntityType, Biome, Enchantment). The description adds a slight redundancy by listing similar examples but contributes no new semantic meaning beyond the schema.

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 names a specific verb ('Get') and resource ('Minecraft/Forge/NeoForge registries') with concrete examples (Block, Item, EntityType), making the tool's scope clear. It is implicitly distinct from sibling tools like get_document and get_api_detail, though it does not explicitly name a differentiating sibling.

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 about when to use this tool versus alternatives such as search_api or get_api_detail. The description implies the use case (querying registry information) but provides no conditions, exclusions, or sibling routing.

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