clear_item_in_out

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

Description adds minimal context beyond annotations: 'reset to full duration' clarifies the outcome. Annotations already indicate non-read-only (readOnlyHint=false). No mention of edge cases (e.g., locked items) or 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?

Single sentence, front-loaded with verb and resource, no filler. Highly concise and wastes no words.

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?

For a simple tool with 3 parameters and no output schema, the description is adequate. It covers the action and result. Minor gap: no mention of default behavior (both points cleared) or item type context.

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 coverage is 100%, so baseline is 3. Description briefly mentions 'in and/or out points' matching the boolean parameters but adds no further semantics beyond schema descriptions.

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?

Description clearly states the verb 'Clear' and the resource 'in and/or out points on a project item' with the effect 'reset to full duration'. It is specific and distinguishes from sibling tools like 'set_item_in_out'.

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 implies usage for clearing in/out points but does not explicitly state when to use this tool versus alternatives like 'set_item_in_out'. No exclusion criteria or prerequisites are mentioned.

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