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

No annotations are provided, so the description carries the full burden. It states the operation is a 'Get', implying read-only behavior, and adds the note that the task_ref is 'opaque', which is useful. However, it doesn't mention return format, permissions, or idempotency. For a simple get tool, this is adequate but not rich.

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, front-loaded sentence that conveys the action and the source of the parameter without any fluff. Every word earns its place.

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 tool with one parameter and no output schema, the description is nearly complete. It tells what it does and where to get the parameter. It doesn't explicitly describe the return structure, but 'Get one task' implies the task object, and the reference to google_ads_tasks_list likely establishes the structure. Minor gap, but acceptable for a simple get.

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?

With 0% schema description coverage, the description compensates by explaining that task_ref is the opaque reference returned by google_ads_tasks_list. This tells the agent exactly where the value comes from and that it should not be modified or interpreted. This is essential context beyond the bare type string.

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 verb 'Get' and the resource 'task', and specifies that the task is identified by the task_ref from google_ads_tasks_list. This distinguishes it from listing tools and status tools, making the purpose unambiguous.

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?

It explicitly states the parameter comes from google_ads_tasks_list, implying when to use this tool: after listing tasks and when you need a specific task's details. It doesn't explicitly exclude alternatives like tasks_get_status, but the context is clear enough for an agent to infer the appropriate usage.

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