update_subtask

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

Discloses partial update behavior and status mapping. No annotations, so description carries burden. However, it doesn't mention write effects, idempotency, or permissions.

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?

Concise single paragraph with no wasted words. Front-loaded purpose, followed by clear constraints, all in two 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?

With empty schema and no output schema, the description is incomplete. It omits parameter types, required vs optional status per field, and return value details. The tool cannot be reliably used without additional info.

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 input schema is empty but the description references multiple parameters. This mismatch is critical; the agent cannot map described fields to schema properties. Baseline for empty schema should be compensated by description, but it fails to provide types or formal definitions.

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 it updates an existing subtask with partial updates, distinguishing it from create and delete siblings. However, the missing input schema may cause confusion.

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?

Explicitly states required identity fields (subtask_id, task_id) and that at least one field among title, status, user_id, time_estimated, or time_spent must be provided, giving clear usage conditions.

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