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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is largely covered. The description adds two genuinely new behavioral facts: the write commits immediately with no confirmation step, and the agent should echo back the created item. It does not say what is returned (id, defaults applied) or how visibility defaults are resolved.

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?

Two compact sentences with the core action and the optional micro-actions front-loaded, followed by the operational cautions. No filler; only slight compression cost from packing commit/confirm/dedup into one semicolon clause.

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 9-parameter mutation with no output schema and low schema coverage, the description covers creation, immediacy, and de-duplication but leaves enum selection, defaults, and required-field interactions unaddressed. An agent could call it, but would likely guess on type/visibility/owner.

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?

Schema description coverage is only 22% across 9 parameters, and the description covers just title and micro_actions. It says nothing about the type enum (decision, follow_up, project, routine_instance, errand, repair), the energy enum, visibility, owner_id, or estimated_minutes, so the agent gets no help choosing among seven task types or knowing whether an omitted owner defaults to the caller.

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?

States a specific verb and resource ('Create a household task') and clarifies that micro-action steps are optional and embedded. It is distinguishable from bulk_create_tasks by the singular framing and the anti-duplication note, though no sibling is named explicitly.

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?

Gives a clear when-not-to-use condition ('don't duplicate an item already in context') and a post-call behavior (confirm back what was created). It stops short of naming alternatives such as bulk_create_tasks or break_down_task for decomposing an existing task into steps.

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