google_tasks_create_task

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

No annotations are present, so the description carries the full burden. It only discloses the RFC 3339 timestamp format for due dates. It does not mention authentication, default tasklist behavior, side effects, or return values, leaving the agent under-informed for a mutation operation.

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 short and front-loaded with 'Create a Google Task', and the due date example is a useful addition. However, it is under-specified rather than genuinely concise; it omits critical parameter explanations that would fit naturally in a few more sentences.

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?

Given the tool has 6 parameters, no annotations, and no output schema, this description is incomplete. It does not clarify what the tool returns, how tasklistId defaults to '@default', or the semantics of parent/previous relationships, making it difficult for an agent to invoke it correctly without additional assumptions.

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 a schema description coverage of 0%, the description must compensate for all six parameters. It only adds format details for 'due', leaving title, notes, parent, previous, and tasklistId unexplained beyond their raw schema types. This is insufficient for a tool with this many parameters.

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 explicitly states 'Create a Google Task', using a specific verb and resource. This clearly distinguishes it from sibling tools like update, delete, and list, which involve different actions.

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 vs alternatives, nor any mention of prerequisites or exclusions. The verb 'Create' implies usage, but no explicit context is provided.

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