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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals critical traits: atomicity, replacement semantics (old parent link deleted, not added), the requirement for npub for billing, and the extra billed read when confirm=True. These are substantive details beyond the schema fields.

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 three sentences with no redundancy. It front-loads the purpose, then delivers the most important behavioral caveat (replacement), and ends with a practical pointer to the alternative tool. Every sentence 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?

For a mutation tool with 7 parameters and no annotations, the description covers the essential context: what the operation does, how it behaves (atomic, destructive to old parent link), authentication/billing requirements, and a pointer to alternatives. The presence of an output schema means return values need not be explained, and the description is sufficiently complete for an agent to select and invoke the tool correctly.

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 86%, so the baseline is 3. The description adds little parameter-specific meaning beyond the schema; the only addition is the mention of npub for billing, but that is already in the schema. The replacement semantics for new_parent_id are also already described in the schema ('replaces all current parents'). Thus the description does not significantly enhance parameter understanding.

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 opens with 'Atomically reparent and/or retype a thought in one operation,' which uses specific verbs and identifies the resource (a thought) and the operation (reparent/retype). It distinguishes itself from sibling tools by explicitly referencing update_thought as the alternative for setting name/label, clarifying its unique scope.

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 when-to-use guidance by stating the operation's specificity (reparent/retype in one atomic call) and explicitly directs users to update_thought for setting name/label, including the note that update_thought now accepts new_parent_id. This gives an explicit alternative and exclusion criterion.

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