Jobs-tools-knowledgeBase-autoManageNotes

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It does state the promotion and archival actions and the triggering criteria, but it omits side effects, reversibility, destructive nature, permission requirements, or return value. For a tool that mutates note storage, this is a significant transparency gap.

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?

Two sentences, front-loaded with the main purpose and immediately followed by concrete behavioral detail. Every word earns its place; no fluff or redundancy.

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 has no annotations, no output schema, and zero parameters, but the description explains its core purpose and behavior. Still, it lacks details about invocation expectations, what 'long-term memory' and 'archive' concretely mean, whether the operation is reversible, and what the result looks like—leaving the description only partially complete for an agent.

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 is empty with zero parameters, so there are no parameter semantics to explain. The description's mention of access count and recency adds context about internal decision criteria but is not required to document parameters. Baseline of 4 is appropriate.

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?

Description uses specific verb 'Auto-manages' with resource 'notes' and clearly scopes behavior to Zettelkasten lifecycle: promoting frequently accessed notes to long-term memory and archiving rarely used notes based on access count and recency. This clearly distinguishes it from sibling tools like promoteToLongTerm and archiveNote by describing an automated aggregate behavior.

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?

Usage is implied through 'based on usage patterns in Zettelkasten lifecycle'—the agent can infer this is for automatic lifecycle management. However, there is no explicit statement of when to choose this over manual alternative tools, nor exclusions or prerequisites.

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