promote_to_org

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

The main behavior is disclosed (changing a memory from private to org visibility) and the required permissions are stated. However, key behavioral controls in the schema—especially the 'action' enum values and 'dry_run' flag—are unexplained, and no annotations exist to fill that gap.

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 brief sentences with no redundant words or filler. It front-loads the core purpose and then states the key precondition, making it easy to parse quickly.

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 lack of annotations and output schema, the description is not complete enough for reliable invocation. It omits the semantics of the 'action' enum, the behavior of 'dry_run', expected outcomes, and any edge cases or error conditions.

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?

With zero schema descriptions, the description must compensate. It implicitly covers node_id and org_id ('own the node', 'target org'), but it does not explain the meaning or effects of 'action' or 'dry_run'. Coverage is partial at best.

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 primary action: promoting a private memory to org visibility. It also names the resource ('private memory') and the target state ('org visibility'), and it is distinct from sibling tools like pin_memory or memory_store.

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 a precondition ('Caller must own the node and belong to the target org') but does not say when to use this tool versus alternatives like pin_memory or memory_store. No explicit usage guidance or comparison to sibling tools is given.

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