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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds only the 'previous activity' framing; it says nothing about cursor pagination, archive scope, or result shape. Adequate but thin on top of rich annotations.

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?

One sentence with no filler, and the distinguishing clause ('separate from generated media') is placed at the end where it still parses cleanly. It is lean to the point of under-specification, but nothing is wasted.

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 9-parameter, multi-enum search tool the description gives no filter semantics, no mention of the kind=text default, no cursor/limit paging guidance, and no archive behavior. An output schema and annotations exist, but the parameter surface is left entirely unexplained.

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% across 9 parameters, so neither the schema nor the description explains what kind, lang, archive, cursor, model_key, or the date bounds mean. The 'text and template' phrasing loosely maps to the kind enum, but that is the only hint provided.

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?

States a specific resource (previous text and template activities) and draws a contrast with generated-media history, which implicitly separates it from sibling aimixer_history. The verb 'Find' is generic and no sibling is named explicitly, but an agent can tell what domain this covers.

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?

'Separate from generated media' implies the alternative (aimixer_history / aimixer_history_search) without naming it, so routing is inferable but not stated. No explicit when-to-use, when-not-to-use, or prerequisite guidance.

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