generate_context_zip

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

No annotations are provided, so the description carries the burden. It states that knowledge is packaged into a ZIP archive, implying a read/export operation, but it does not disclose side effects (e.g., whether existing files are overwritten), prerequisites, or scope (e.g., all projects by default). The description adds some context but not deep behavioral detail.

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, front-loaded sentence with no redundant words. It immediately states the action and purpose, and every phrase contributes meaning.

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?

With 5 parameters, no annotations, and no output schema, the description is minimal. However, the schema fully documents all parameters, and the tool's purpose is simple (zip creation). It would benefit from noting default behavior (e.g., includes all projects/branches) and whether the ZIP replaces existing files, but it is not severely incomplete.

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%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides. The schema itself includes informative descriptions for includeTypes and projectNames, so no significant gap exists.

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 'Package' and identifies the resource 'Cursor-Cortex knowledge' with a clear output: 'a portable ZIP archive for sharing between users and environments'. This clearly distinguishes it from sibling tools that read, write, or search individual knowledge items.

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 conveys the context for use ('for sharing between users and environments') without explicitly listing when not to use it or naming alternatives. It is clear enough that an agent would know to use this tool for packaging knowledge, while siblings cover other operations. No exclusions are mentioned, but the intent is explicit.

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