MemoryMesh

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

With no annotations provided, the description carries full burden for behavioral disclosure. 'Add' implies a write/mutation operation, but the description doesn't address permissions needed, whether NPCs can be modified or deleted later, what happens on duplicate names, or what the response looks like. For a creation tool with zero annotation coverage, this leaves significant behavioral questions unanswered.

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, efficient sentence that gets straight to the point with zero wasted words. It's perfectly front-loaded with the core purpose, making it immediately understandable despite its brevity.

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 creation tool with complex nested parameters (17 properties within the npc object), no annotations, no output schema, and 0% schema description coverage, the description is severely inadequate. It identifies what the tool does at a high level but provides none of the operational details needed to use it effectively in the context of the knowledge graph system.

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 0%, meaning none of the 17 nested properties within the 'npc' object have descriptions in the schema. The tool description provides absolutely no information about parameters beyond the existence of an 'npc' object, failing to compensate for the complete lack of schema documentation. This leaves the agent guessing about what data to provide.

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 action ('Add') and resource ('Non-Player Character (NPC) to the knowledge graph'), making the purpose immediately understandable. It distinguishes from some siblings like 'add_artifact' or 'add_location' by specifying NPCs, but doesn't explicitly differentiate from 'add_player_character' or other character-related tools.

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 provides no guidance on when to use this tool versus alternatives. With siblings like 'add_player_character', 'update_npc', and 'delete_npc', there's no indication of when this creation tool is appropriate versus modification or deletion tools, or how it relates to other entity types in the knowledge graph.

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