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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds essentially nothing beyond safety – 'recent' hints at a time window but no pagination, ordering, or filtering behavior is disclosed, so it earns little credit above the annotation baseline.

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?

A single short sentence that is front-loaded and wastes no words. Its brevity, however, reflects under-specification rather than disciplined concision, so it is adequate but not strong.

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 the six filter/pagination parameters are undocumented and no usage context is provided. For a 6-parameter listing tool the description is materially incomplete.

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 6 parameters (days, limit, cursor, search, status, connection_context), leaving the description to compensate – but it does not. 'Recent' vaguely gestures at the days window, yet limit, cursor, search, and status carry no explanation anywhere.

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 verb ('List') and resource ('create/copy history'), so an agent knows the general shape of what it retrieves. However, it does not differentiate itself from closely named siblings such as tasks_list, tasks_latest, or tasks_get_create_detail, leaving overlap resolution to inference.

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 when-to-use context, no exclusions, and no mention of the sibling tools it competes with (tasks_list, tasks_latest). The agent gets no guidance on which task-history tool to select under which condition.

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