Move a attached to the deal task

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

With no annotations, the description must carry the behavioral burden, but it only states 'Move a attached to the deal task' and provides the HTTP method. No disclosure of what the move does (e.g., reorder, change parent), whether it is destructive, or what permissions are required. The agent remains uninformed about side effects.

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 short, which is efficient, but it lacks essential information. It front-loads the HTTP method and path, which is good, but the remaining content is redundant or unhelpful. It earns a 3 for brevity but loses points for not earning its place with substance.

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 the tool's complexity (nested parameters, no annotations or output schema), the description is severely incomplete. It does not explain what a 'move' entails, what the response looks like, or how to use the parameters. For a tool with many siblings, this lack of context makes it nearly impossible to use correctly.

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 0%, yet the description adds no parameter explanations. It only mentions 'Body: application/json'. The schema has nested objects with properties like 'previousTaskId' (with a description in the schema) and path parameters, but the description does not clarify them. The agent must infer meaning solely from the schema, which is insufficient.

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 'Move a attached to the deal task' is vague and nearly identical to the title. It fails to specify what is being moved (a task within a deal's task order?) and does not distinguish it from sibling move tools like 'weeek_move_a_deal' or 'weeek_move_board'. The HTTP path and tag provide technical context but not clear purpose.

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 the many other move-related tools. There is no mention of prerequisites, context, or exclusions. The agent has no basis to choose this over alternatives.

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