MemoryMesh

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool deletes an artifact, implying a destructive, irreversible operation, but doesn't specify permissions required, confirmation prompts, side effects (e.g., impact on related graph elements), or error handling. This is inadequate for a mutation tool with zero annotation coverage.

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 poorly structured with unnecessary line breaks ('Delete\n an existing\n artifact\n from\n the\n knowledge\n graph'), making it less readable. While the content is minimal, the formatting wastes space and disrupts flow. A single, clean sentence would be more effective.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks critical details: what happens post-deletion (e.g., success confirmation, error messages), whether deletion is permanent, and how it interacts with the knowledge graph system. The agent has insufficient context to use this tool safely and effectively.

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%, with the parameter 'name' documented as 'The name of the artifact to delete'. The description adds no additional parameter information beyond what's in the schema, such as format examples or constraints. Since the schema fully covers the single parameter, the baseline score of 3 is appropriate.

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 ('Delete') and resource ('an existing artifact from the knowledge graph'), making the purpose immediately understandable. It distinguishes itself from sibling tools like 'add_artifact' and 'update_artifact' by specifying deletion rather than creation or modification. However, it doesn't explicitly mention what an 'artifact' is in this context, which slightly reduces specificity.

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. It doesn't mention prerequisites (e.g., artifact must exist), exclusions (e.g., cannot delete if referenced elsewhere), or comparisons to siblings like 'update_artifact' for modification instead of deletion. The agent must infer usage from the tool name alone.

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