nyarhi_xavani_import

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

With no annotations provided, the description must carry the transparency burden. It adds useful context by stating the operation is 'read-only and sync-only' and that 'nothing leaves the machine,' which informs the agent about safety and privacy. However, 'read-only' is ambiguous given that an import would write to the graph, and it does not disclose whether existing graph data is overwritten or if the operation is idempotent.

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 two sentences with clear front-loading of the primary purpose and a compact second sentence adding behavioral context. Every word contributes; there is no redundancy or filler.

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 absence of annotations and parameter descriptions, the description is too thin for a 2-parameter import tool with no output schema details. It does not explain what 'home' and 'store' refer to, whether the graph is modified, or how this interacts with other nyarhi graph operations. The privacy note is helpful but leaves significant knowledge gaps.

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 has two parameters (home, store) with 0% description coverage, and the description does not explain their meaning or how they relate to 'local Xavani home data.' The names alone are insufficient for an agent to infer what values to provide, making parameter usage speculative.

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 uses a specific verb ('import') and identifies both the source ('local Xavani home data') and destination ('into the graph'), clearly distinguishing this tool from sibling tools like nyarhi_add_node or nyarhi_search. It also specifies the data types (memories and sessions), which further clarifies its unique role.

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 clear context: use this tool when you need to import local Xavani home data into the graph. It implies a specific use case and differentiates from other nyarhi tools by focusing on bulk import of home data, but it does not explicitly mention alternatives or exclusion criteria, so it lacks the 'when not to use' guidance found in top-tier examples.

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