mc_entity_details

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

The description discloses what information is included (equipment slots with damage, custom names, mounted vehicle, passengers, attributes, frame contents) and the special return case ({gone: true}) for despawned or unloaded entities. No annotations are provided, so the description carries full burden and does it well.

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 concise: two sentences covering main purpose, included details, and edge case. Every sentence adds value, and the information is front-loaded.

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?

Given no annotations and no output schema, the description covers the tool's behavior well but does not specify error handling for invalid ids beyond the gone case. It is fairly complete for a single-parameter tool.

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 schema covers 100% of the single parameter with a basic description. The tool description adds context by specifying the id sources (mc_nearby_entities or mc_looked_at_entity), adding value 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 clearly states the tool's purpose: 'Get full details for one entity by id'. It specifies the source of the id (from mc_nearby_entities) and distinguishes from sibling tools like mc_nearby_entities (listing) and mc_looked_at_entity (getting looked-at entity).

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 indicates when to use the tool (to get details for a specific entity) and what the id should come from. It does not explicitly state when not to use it or mention alternatives, but the context is clear given sibling tools.

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