update_task

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

Description reveals important behavioral detail: 'update_fields is required by Feishu' and explains the effect. No annotations provided, so burden is on description. Missing disclosure of permissions, side effects, or output, making it moderately transparent.

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 sentences with no wasted words. Front-loaded with purpose, then critical context on the required parameter. Excellent efficiency.

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 no output schema and no annotations, description covers core purpose and a key parameter quirk. Lacks details on return values, error conditions, or prerequisites. Adequate but not comprehensive.

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 coverage is 100%, baseline 3. Description adds value by explaining that 'update_fields' lists fields to update and that Feishu ignores other keys in 'task'. This clarifies usage beyond schema alone.

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?

Description clearly states 'Patch a task' with specific verb and resource. However, it does not differentiate from sibling tools like 'complete_task' or 'delete_task', which limits clarity for selection.

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?

Implied usage: use when updating a task. No explicit guidance on when not to use or alternatives. The description mentions the Feishu requirement, which aids correct invocation but not context of use.

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