scheduling_remove_line_item

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

No annotations provided. Description only states removal and confirmation, but fails to disclose side effects, prerequisites, or error handling. Heavily reliant on short text.

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 user instruction.

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?

No output schema. Description fails to explain post-removal effects, return values, or failure scenarios. Incomplete for a simple removal operation.

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?

Input schema has 100% coverage with clear descriptions. Description reinforces the 'confirmed' requirement (already in schema), adding minimal value.

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?

Explicitly states 'Remove a line item from a schedule', with specific verb and resource. Distinguishes from siblings like scheduling_add_line_item and scheduling_update_line_item, and from tickets_remove_line_item by context.

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?

Includes required confirmation ('user MUST confirm'), but no when-to-use or when-not-to-use guidance. Does not differentiate from similar tools like scheduling_add_line_item or tickets_remove_line_item.

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