zero_capture

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 discloses 'no validation', but fails to explain other behavioral traits like whether the capture is persistent, what happens to the data, or if there are side effects. Minimal transparency.

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?

A single sentence that conveys the core purpose and key behavior. No redundant or unnecessary information. Front-loaded with the most important details.

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 capture tool with no output schema, the description should explain what happens after capture (e.g., return value, side effects). It only mentions the target and lack of validation, leaving significant gaps for an agent to understand the tool's full behavior.

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 already describes both parameters (text and domain) with 100% coverage. The description adds context about the target folder ('00_Fleeting'), but this does not add significant semantic meaning beyond the schema.

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 states the verb 'capture' and the target '00_Fleeting', with traits 'lightest, no validation'. This clearly identifies the tool's purpose and distinguishes it from siblings like zero_write_note. However, it is in Thai, which may reduce clarity for non-Thai-speaking agents.

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?

Implies use for quick capture without validation, but no explicit context about when to use this tool versus alternatives like zero_resolve or zero_write_note. The description does not provide when-not or alternative guidance.

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