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

With no annotations, the description carries the behavioral burden and covers the non-obvious quirks: due times are discarded, priority is not supported, and parentTaskId creates a subtask. It does not describe return values or side effects, but the disclosure is substantial for a create tool.

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?

Three sentences, all informative: the core action is front-loaded, and each following sentence adds a distinct behavioral caveat. There is no filler or repetition of the schema except where it reinforces an important quirk.

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 description is sufficient for a simple creation call, but with no output schema or annotations it leaves out how to obtain listId, which fields are required, and what the tool returns. The behavioral caveats are useful, yet an agent still needs to infer some setup and postconditions.

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 description partially compensates for the 50% schema coverage by restating the due-date behavior and the subtask meaning of parentTaskId in natural language, and it warns that no priority parameter exists. But notes, listId, and title still have no semantic explanation beyond their names, and most of the parentTaskId/dueDate content duplicates schema descriptions.

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 opens with a specific action and object — 'Add a task to a list' — and the title/name confirm it creates a Google task. It is distinguishable from siblings like create_google_task_list and complete_google_task by naming task creation, though it does not explicitly contrast with update/complete variants.

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?

'Add a task to a list' conveys the core use case, and the subtask note adds a creation variant, so usage is implied. However, there is no explicit guidance about when to prefer this over complete_google_task, update_google_task, or list_google_tasks, and no exclusions or prerequisites.

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