bulk_resolve_tasks

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

There are no annotations, so the description must disclose behavioral traits. It only mentions 'mutation' and shows closeCode/closeNote, but fails to state side effects, irreversibility, required permissions, or what happens to the tasks. The mutating nature is implicit but not explained.

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 very short and gets to the point quickly. However, the line 'Variables: input' is redundant with the schema, and the opening 'Tasks · mutation bulkResolveTasks' is somewhat tautological. Still, it is efficient and not bloated.

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?

There is no output schema and no description of the return value, effects on tasks, or bulk-specific considerations. The example provides input shape but leaves the agent without information about what the mutation accomplishes beyond the name's implication.

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's description for 'input' is just 'GraphQL: BulkResolveTasksInput!', which is uninformative. The tool description's example variables JSON adds structure by showing closeCode, closeNote, and taskIds, providing the agent with concrete usage that the schema lacks. customer_slug is already described in the schema.

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 repeats the tool name as 'mutation bulkResolveTasks' and provides example variables, but it does not explicitly state 'Bulk resolve tasks' in plain language. The example with taskIds and closeCode implies the action, but the purpose remains vague without a clear verb+resource statement.

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?

No guidance is given on when to use this tool versus alternatives like resolve_task or bulk_close_incidents. The description only shows an example input, with no mention of contexts, prerequisites, or exclusions.

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