search_and_inject_memory

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

No annotations are present, so the description carries the full burden. It states 'returns' but the tool name includes 'inject', creating ambiguity about whether it modifies state. No behavioral traits (e.g., side effects, permissions, rate limits) are disclosed.

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 a single sentence, which is concise, but it sacrifices substance. It is front-loaded with key terms but lacks the detail needed for effective use.

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?

Given 8 parameters, a complex behavior (search and inject), and no output schema or annotations, the description is entirely inadequate. It does not explain inputs, outputs, or behavior, leaving the agent without essential information.

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 0%, and the description provides no information about any of the 8 parameters. The agent has no clue what parameters like 'task_description', 'injection_mode', or 'fill_from_project' mean or how to use them.

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 states 'returns a context top injection block immediately after a new session/compaction' but does not clearly explain what the tool does. The verb 'returns' is vague, and the resource 'context top injection block' is not defined. It fails to distinguish from sibling tools like inject_relevant_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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of context, prerequisites, or when not to use it. The sibling tool 'inject_relevant_memories' likely serves a similar purpose, but the description offers no differentiation.

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