edit_item

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does an above-average job by revealing non-obvious sentinel behaviors (empty string/zero skipping updates, single space to clear description, -1 to skip parent, 0 to remove parent). It stops short of mentioning side effects, permissions, or error handling, but the critical edge cases are transparent.

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 two sentences with no fluff. The first sentence states the purpose concisely; the second delivers critical usage details in a structured note. Every word earns its place.

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 moderate complexity (6 params, no output schema, no annotations), the description covers the primary purpose and the trickiest behavioral nuances. It doesn't mention the return value or error conditions, but the essential information for calling correctly is mostly present. A slight gap is the lack of guidance on how to use parent_id in conjunction with set_parent at the system level.

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?

Although schema property descriptions are tautological ('title parameter', etc.), the tool description adds real semantic value by explaining how to use sentinel values for each field, especially for parent_id and complexity. It clarifies that zero means 'no update', which is not inferable from the schema. However, it does not provide ranges or constraints for priority/complexity beyond the sentinel.

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 uses the specific verb 'Edit' and clearly lists the resource ('an existing item') plus the editable fields ('title, description, priority, complexity, and/or parent'). This distinctly differentiates it from siblings like new_item (create), delete_item (destroy), and set_parent (parent-only update).

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 provides clear context that this tool is for editing existing items, implying it is not for creation. The note about sentinel values ('Empty string/zero means don't update', 'To clear description, use a single space') offers practical usage guidance. However, it does not explicitly contrast with alternatives such as set_parent, which could also handle parent updates.

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