MemoryMesh

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. It states the tool adds artifacts but doesn't clarify if this is a write operation, what permissions are needed, whether it's idempotent, or how conflicts are handled (e.g., duplicate names). This leaves significant gaps for a mutation tool with no safety or operational context.

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 directly states the tool's purpose without unnecessary words. It's front-loaded and wastes no space, making it easy to parse quickly.

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 mutation tool with no annotations and no output schema, the description is insufficient. It doesn't explain what happens on success (e.g., returns an ID), error conditions, or behavioral traits like idempotency. Given the complexity of adding structured data to a knowledge graph, more context is needed to guide effective use.

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 description mentions 'artifact or unique item' but doesn't detail what parameters are required or their meanings. With 0% schema description coverage, the schema fully documents the single nested parameter 'artifact' and its properties. The description adds minimal value beyond implying the parameter's purpose, aligning with the baseline for high schema coverage.

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 the target ('a new artifact or unique item to the knowledge graph'), which distinguishes it from other 'add_' tools that target different entities like currencies or locations. However, it doesn't explicitly differentiate from 'update_artifact' or 'delete_artifact' in terms of when to use each, keeping it from a perfect score.

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 like 'update_artifact' or 'delete_artifact', nor does it mention prerequisites such as whether the artifact must be unique or if there are constraints on adding duplicates. It lacks explicit usage context beyond the basic action.

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