manage_problem_task

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

With no annotations, the description carries full behavioral burden. It discloses that the action parameter controls the operation and provides required fields per action, status mapping, and date format. It does not mention side effects such as whether deletions are permanent, permission requirements, or list pagination, leaving some behavioral ambiguity for a CRUD tool.

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 structured as a clean docstring with an Args block. It is reasonably concise, with each line earning its place, though the indentation and repeated 'required' notes add minor bulk. The primary purpose is front-loaded.

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 10 parameters and 5 possible actions, the description covers parameter semantics and action-specific requirements well. It does not address list pagination, error handling, or permission prerequisites, but the presence of an output schema covers return values. This is a solid, adequate description for a CRUD tool in this tool family.

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 provides only types and titles with zero descriptions. The description compensates thoroughly by enumerating valid action values, specifying which parameters are required per action, mapping status integers to labels, defining due_date as ISO datetime, and explaining notify_before in hours. This adds essential meaning beyond 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 clearly states it manages tasks on a Freshservice problem, and the action parameter enumerates list/get/create/update/delete, making the CRUD purpose explicit. It distinguishes from sibling tools like manage_problem_note and manage_problem_time_entry by focusing specifically on tasks.

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 action-specific parameter requirements (e.g., task_id required for get/update/delete, title required for create), which gives clear context for invocation. However, it does not explicitly state when to use this tool versus other sibling task management tools, and there are no exclusionary or alternative guidance.

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