search_global_memory_archive

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

Discloses the return structure (success, entries, count) and permission requirement. Since annotations are absent, the description carries the full burden; it covers key behavioral aspects for a read-only search tool.

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?

Well-structured with Args and Returns sections, no fluff. Could be slightly more concise, but all sentences add value.

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?

Covers basic purpose, permissions, and return format. With 4 parameters and no annotations, it adequately explains the tool but lacks mention of pagination or behavior for large result sets.

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?

Lists all four parameters with brief descriptions, compensating for 0% schema coverage. However, it claims caller_agent_id is required, conflicting with the schema where it's optional with a default of null. Also lacks details on tag format and limit default (10).

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?

Clearly states it searches the global archive across all projects. The verb 'search' and resource 'global memory archive' are specific. However, it does not explicitly distinguish from 'search_memory_archive', which likely searches per-project archives.

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?

Provides a permission constraint (Owner/Admin only) and a required parameter caller_agent_id, but offers no guidance on when to use this tool versus similar siblings like list_global_memory_archive or restore_from_global_memory_archive.

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