scheduling_update_line_item

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

Description only says 'Update' without any behavioral details. With no annotations, the description should disclose whether it's a partial update, side effects, or idempotency. The brief description fails to convey important behavioral traits.

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?

Single sentence with no wasted words. However, it is too brief and lacks structure; still, conciseness alone does not detract significantly.

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 complexity (12 parameters, no output schema, no annotations), the description is severely incomplete. It does not explain return values, behavior, or usage constraints, leaving large gaps for an AI agent.

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 only 17% (2 of 12 parameters have descriptions). The tool description adds no additional parameter information. For low coverage, the description should compensate but does not.

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 'Update a line item on a schedule'. The verb 'Update' and the resource 'line item on a schedule' are specific. It distinguishes from sibling tools like scheduling_add_line_item and scheduling_remove_line_item.

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 on when to use this tool vs alternatives. Sibling tools for adding/removing line items exist, but the description does not differentiate usage context or prerequisites.

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