delete_assignment

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

No annotations provided, so description fully bears transparency burden. It discloses cascading deletion: 'Removes the recursive group and every slot that references it.' This is key behavioral context beyond the basic operation. Could mention irreversibility but sufficient.

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?

Description is brief, front-loaded with purpose, then parameters, then return value. Every sentence adds value with no redundancy. Well-structured for agent parsing.

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 simplicity (2 params, output schema exists), the description covers key aspects: action, effect (cascading deletion), prerequisite, parameters, and return type. Could mention error handling or irreversibility, but overall complete for its scope.

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 has 0% description coverage. Description adds basic meaning: id_activity is 'Activity ID', delete_recursive_group_slot is 'Group ID to delete'. This clarifies purpose but lacks detail on why both are needed or expected value ranges.

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 deletes an assignment group and all its time slots. It uses specific verbs and identifies the resource. Among sibling tools, it is distinct from delete_node, delete_message, and other assignment operations.

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?

Provides explicit prerequisite: 'Use get_activity first to find the group ID.' This guides the agent on necessary prior steps. No exclusion or alternative tools mentioned, but the context is clear.

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