wick_export

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. However, 'export' implies a read-only operation, and the description does not mention any side effects or additional behaviors. It adds no explicit safety or auth context, which is acceptable for a simple export but still leaves ambiguity about the exact behavior.

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, focused sentence with no filler. It front-loads the action and resource, then lists formats, achieving high information density.

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?

The tool is simple with one optional parameter and no output schema. The description adequately covers what the tool does and the formats available. It lacks details about the return mechanism or any caveats, but given the simplicity, it's close to complete.

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 one optional parameter 'format' with enum values, but the schema description coverage is 0%. The description compensates by explicitly listing 'JSON, CSV, or a Markdown table', which restates the enum in natural language and clarifies the meaning. It adds value beyond the raw schema, though it doesn't detail each format's nuances.

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 'Export' and resource 'session data', listing three concrete output formats. This clearly distinguishes it from sibling tools like wick_track or wick_status, which have different purposes.

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 implies usage when a user needs to export session data, but it does not provide explicit guidance on when to choose this tool over alternatives or mention any exclusions. Sibling tools are not referenced, so the agent must infer the appropriate context based on the tool name and purpose alone.

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