set_parent

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

With no annotations, the description carries the burden of behavioral disclosure. It reveals the special mechanism for removal (parent_id=0), but doesn't discuss side effects like replacing an existing parent, error conditions, or response format. Minimal but not completely absent.

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 short sentences with no wasted words. The primary purpose is stated first, and the removal idiom follows as a necessary clarification.

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 two-parameter setter with no output schema, the description adequately covers the core operation and the non-obvious removal idiom. It lacks details on return value or errors, but the tool's simplicity doesn't demand more.

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?

The schema descriptions are tautological ('item_id parameter'), so the description adds critical meaning by explaining that parent_id=0 removes the parent. This goes beyond the schema and clarifies the special semantics of parent_id. item_id remains self-evident.

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 the tool's function with a specific verb ('set' or 'remove') and resource ('parent relationship'). It distinguishes itself from sibling tools like add_relationship/remove_relationship by focusing specifically on the parent relationship.

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 gives clear context for when to use the tool (to set or remove a parent relationship) and provides a specific usage rule ('Use parent_id=0 to remove parent'). It doesn't explicitly mention alternatives, but the sibling names make the differentiation apparent.

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