Project Tessera

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

No annotations are provided, so the description carries the full burden. It mentions the tool exports memories for AI platform use, which implies read-only behavior, but doesn't specify permissions needed, rate limits, or what exactly gets exported (e.g., format details, scope). It adds some context about migration purpose but lacks comprehensive behavioral details.

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 zero waste: the first explains what the tool does and lists targets, the second provides clear usage guidance. It's appropriately sized and front-loaded with essential information.

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 1 parameter with low schema coverage and an output schema present, the description is reasonably complete. It covers purpose, usage, and parameter meaning, but lacks details on behavioral aspects like permissions or export scope. The output schema likely handles return values, so the description doesn't need to explain those.

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 input schema has 1 parameter with 0% description coverage. The description compensates by explaining the 'target' parameter's purpose and listing the three supported values ('chatgpt', 'gemini', 'standard'), which adds meaningful semantics beyond the bare schema. However, it doesn't detail default behavior or format specifics.

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 tool's purpose with a specific verb ('Export') and resource ('memories'), specifying it's for use in another AI tool. It distinguishes from siblings like 'export_knowledge' or 'export_memories' by focusing on AI platform migration formats rather than general exports.

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 explicitly states when to use this tool: 'Use this when migrating knowledge to another AI platform.' It provides clear alternatives by listing supported targets ('chatgpt', 'gemini', 'standard'), helping the agent choose the appropriate format for the specific migration scenario.

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