create_task

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

The description discloses the placement behavior based on scheduled_date, which is useful, but does not mention other behavioral traits such as authorization requirements, idempotency, or return value, leaving some behavioral gaps.

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 extremely concise—two sentences—and front-loads the core action, making it easy to parse with no unnecessary words.

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 15 parameters, no output schema, no annotations, and many siblings, the description is too sparse; it lacks guidance on how to use most parameters, error conditions, and differentiation from similar tools like create_calendar_event.

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 only adds meaning for the scheduled_date parameter, leaving the other 14 parameters (e.g., priority, labels, task_type) without additional context beyond their names.

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 tool creates a task and specifies the placement behavior (MyDay vs Inbox) based on the scheduled_date parameter, effectively distinguishing it from siblings like complete_task or update_task.

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?

The description provides context for when to use the tool (creating a task) and a conditional rule for its behavior, but it does not explicitly state when not to use it or mention alternatives among the many sibling create tools.

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