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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only two useful pieces of context: the read is scoped to the authorized Darwin account and is "bounded" (i.e., paginated), with no mention of auth requirements or rate limits beyond that.

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?

Two short sentences with no padding, and the scope statement is front-loaded. However, the brevity here is under-specification rather than disciplined conciseness for a five-parameter tool.

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?

An output schema exists, so return values need not be explained. But with five undocumented parameters, no when-to-use guidance, and no real differentiation from list_threads, the definition is far too thin for an agent to invoke it correctly.

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?

The schema has five parameters (limit, cursor, archived, targetAgent, needsAttention) with 0% description coverage, so the description carries the full burden. It mentions none of them, leaving the agent with no idea what targetAgent, needsAttention, or archived mean in this context.

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 a verb and resource ("List private threads") but this conflicts with the tool name list_act_history, leaving the agent unsure whether the tool lists threads or an activity/audit history. It explicitly says it is "the same bounded read as list_threads," which fails to distinguish it from that sibling rather than clarifying it.

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?

There is no statement of when to use this tool instead of list_threads, get_thread, or list_search_history. Claiming it is "the same bounded read as list_threads" actively obscures the selection decision rather than guiding it.

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