create_org

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

Discloses ownership, tier limitation, response fields (tier, lease times), step-up gating, and potential error code. With no annotations, this fully covers behavioral traits.

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 sentences, no wasted words, front-loaded with the main action, followed by important constraints and response details.

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 tool with one parameter, the description covers creation, inputs, outputs, and a possible error. Could mention that step-up gating is a prerequisite, but overall adequate.

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 has 100% coverage with a good description. The tool description adds extra context (non-unique, not an id, no tier input), enhancing understanding beyond the schema.

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?

Clearly states it creates an empty organization on the prototype tier, with the user becoming owner. Specifies the endpoint and uniquely identifies the action among many sibling tools.

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?

Provides context that it creates on prototype tier, accepts optional display name, and mentions a possible error cap. Doesn't explicitly contrast with alternatives, but is sufficient for the single creation tool.

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