DM20 Protocol

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get NPC information' implies a read-only operation, but it doesn't specify permissions, rate limits, or what happens with invalid inputs. The description is minimal, offering basic intent but lacking details on error handling or output format.

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 extremely concise with 'Get NPC information'—a single, front-loaded sentence that wastes no words. It directly states the tool's purpose without unnecessary elaboration, making it efficient for quick comprehension.

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 the complexity of retrieving NPC data in a game context, with no annotations and no output schema, the description is incomplete. It doesn't explain what information is returned, how NPCs are identified, or handle edge cases. This leaves significant gaps for an AI agent to understand the tool's full behavior and output.

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%, so the schema fully documents the two parameters. The description doesn't add any parameter-specific details beyond what's in the schema, but with high coverage, the baseline is 3. Since there are only 2 parameters and the schema is comprehensive, a score of 4 reflects adequate parameter understanding without extra description input.

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 'Get NPC information' clearly states the verb ('Get') and resource ('NPC information'), making the basic purpose understandable. However, it doesn't distinguish this tool from sibling tools like 'list_npcs' or 'get_character', leaving ambiguity about whether this retrieves a single NPC versus a list, or how NPCs differ from characters.

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 provided about when to use this tool versus alternatives. The description doesn't mention sibling tools like 'list_npcs' (which might list multiple NPCs) or 'get_character' (which might retrieve player characters), nor does it specify prerequisites or appropriate contexts for use.

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