batch_promote

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

Describes the process (scans, chunks, ingests with embeddings) and dry-run mode. But lacks details on side effects (e.g., whether original memories are deleted), idempotency, and authorization requirements. With no annotations, the description should cover more behavioral traits.

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 relatively concise with four sentences, front-loaded with purpose. It covers key points without redundancy, though it could be slightly more streamlined.

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 tool with 5 parameters and no output schema, the description explains the overall workflow and use case. Lacks details on return format and partial failure behavior, but is reasonably complete for guiding an AI 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?

Schema description coverage is 100%, so baseline is 3. Description adds context like 'dry-run mode to preview candidates' but does not significantly expand on parameter meanings beyond the schema. Adequate but not exceptional.

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 verb 'promote' and the resources: from short-term memories (demo.memories) to permanent long-term storage (demo.marsvault_chunks). It distinguishes from siblings like 'demote_memory' by specifying automatic promotion of expiring memories.

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?

Explicitly says 'Use this to prevent valuable context from being lost when short-term memories expire' and mentions dry-run mode for preview. However, it does not explicitly state when not to use it or compare to alternatives like manual insertion.

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