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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that it lists recent history but does not mention whether it is read-only (though implied), what the response contains, pagination behavior, or any side effects. The term 'opaque task references' is undefined, leaving the agent guessing about the output format and its usability.

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, direct sentence with no fluff. It front-loads the core purpose and introduces a key term. While it is minimal, it is efficient and appropriately sized for a simple list operation, avoiding unnecessary verbosity.

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?

The tool is simple (one optional param, no output schema, no annotations), but the description leaves critical gaps: it does not explain what 'opaque task references' are, how the output should be used with other tools (e.g., google_ads_task_get), or whether the limit controls pagination. An agent cannot fully understand the tool's role in the workflow without additional context.

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 coverage is 0% (no descriptions in the input schema), and the tool description does not mention the 'limit' parameter at all. The agent must infer its meaning solely from the schema's default and bounds, which is insufficient for a tool with one parameter that lacks any description. The description fails to compensate for the schema gap.

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 clearly states the action (list) and resource (recent Google AdsAgent task history). It also introduces the key concept of 'opaque task references', which hints at the output nature. However, it does not explicitly differentiate from sibling tools like google_ads_task_get or tasks_get_status, which could also relate to task 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 tool versus alternatives. No mention of prerequisites, filters, or exclusions. An agent would not know if this is the right tool for retrieving a specific task or checking status, given siblings like google_ads_task_get and tasks_get_status exist.

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