create_or_update_organization

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

No annotations are provided, so the description carries the burden. It discloses 'WRITE' (mutation) and 'Idempotent,' which is meaningful behavioral context beyond a simple create/update. However, it omits details like permission requirements, reversibility, or what happens with null external_id.

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 a single sentence, front-loaded with 'WRITE,' and contains zero filler. Every word contributes to understanding the tool's purpose and behavior.

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?

The core logic is clear and an output schema exists, so return values need not be explained. However, the description does not address edge cases like null external_id, multiple matches, or the uniqueness constraint on name, leaving some gaps for a 5-parameter mutation tool with no annotations.

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 only 60%, leaving tags and notes undocumented in both schema and description. The tool description itself does not add any parameter meaning beyond what the schema already provides, failing to compensate for the gaps.

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 action: 'Create an organization, or update it if one matches by external_id.' It specifies the resource (organization) and the distinguishing upsert behavior, setting it apart from sibling tools like create_or_update_user.

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 when to use the tool (when you want to create or update an org by external_id) and notes idempotency, which is a strong usage hint. It does not explicitly name alternatives or exclusions, but the context is clear given the sibling list.

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