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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds only that results are 'summaries' (vs detailed records), but says nothing about the default 7-day window, pagination via cursor/limit, filtering behavior, or what happens with status/task_types filters.

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?

It is a single short, front-loaded phrase with no wasted words. But this is under-specification rather than effective conciseness for a six-parameter paginated list 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. However, for a filtered, paginated list with six undocumented parameters and three similar sibling tools, the description omits everything an agent needs to choose and configure the call 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?

Schema description coverage is 0% and there are six parameters (days, slim, limit, cursor, status, task_types), yet the description mentions none of them. It does not explain units for 'days', what 'slim' returns, or accepted values for status/task_types, so it fails to compensate for the undocumented schema.

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 gives a verb (list) and resource (task summaries) with a recency scope ('recent'), so the basic operation is clear. However, 'task' is ambiguous in a toolset that has create-history tasks, operations, and status tasks, and nothing distinguishes it from siblings like tasks_latest, tasks_get_status, or tasks_list_create_history.

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 guidance on when to use this instead of tasks_latest (a close sibling) or tasks_list_create_history. The agent must open both schemas to infer the difference, so usage is only weakly implied by the word 'recent'.

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