ai_memory_materialize_history

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

Describes fetching from Django and materializing, plus auto-import for opencode. No annotations exist, so description carries full behavioral burden. Lacks info on idempotency, error handling, or side effects like deletion. Moderate 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?

Single sentence conveys purpose and output formats efficiently, no redundancy. Could be slightly better structured by breaking into bullet points, but acceptable.

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?

No output schema; description does not explain return values or behavior of parameters like max_entries, external_id, workspace, or environment. Incomplete for a 7-parameter tool with no output schema.

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 coverage is 100% so baseline is 3. Description adds minimal extra meaning beyond schema (e.g., 'desde la web (Django)' adds context for project parameter). No significant new parameter insights.

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 clearly specifies verb 'materializa' (materializes) and resource 'histórico de sesión' from web (Django) and output formats (prompt file for vscode-copilot/claude, JSON for OpenCode). Distinguishes from sibling tools like ai_memory_list or ai_cloud_pull.

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?

No explicit guidance on when to use this tool vs alternatives, no when-not-to-use or exclusion criteria. Siblings are listed but no comparative advice.

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