inject_relevant_memories

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

No annotations provided. The description mentions 'tiktoken budget' and 'markdown block' but does not disclose side effects, read-only nature, or auth requirements. The comparison to semantic_search_memory is vague. Score 2 for minimal behavioral disclosure.

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 concise (single sentence) and front-loaded with the sibling comparison. However, it lacks structure and relies on external knowledge. Score 3 for reasonable conciseness but limited informativeness.

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?

With 5 parameters, no output schema, and no annotations, the description is too brief. It does not explain the output format, error handling, or budget enforcement. Score 2 for insufficient completeness.

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 0%, yet the description only implicitly references max_inject_tokens via 'tiktoken budget'. Other parameters (query, project_id, session_id, limit) are not explained. Score 2 for insufficient parameter description.

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 states it searches with same scope as semantic_search_memory and creates a markdown block within a token budget. The verb-resource pair is clear enough, but the tool's scope relative to siblings is not fully defined. Score 4 for clear but not fully self-contained purpose.

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 siblings. With tools like memory_search, semantic_search_memory, and search_and_inject_memory, the description fails to differentiate usage contexts. Score 2 for missing usage guidance.

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