create_org

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

No annotations, so description must cover behavioral traits. Discloses ownership, error condition (FREE_ORG_OWNER_LIMIT_EXCEEDED), and tier exclusion. Missing response format or side effects beyond creation.

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: first covers purpose and action, second covers constraints and error. No wasted words, well front-loaded.

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 creation tool with one optional parameter and no output schema, description covers purpose, constraints, and an error. Lacks return value description but still 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 description coverage is 100% with baseline 3. Description adds value by clarifying display_name is non-unique, not an id, and that omitting yields unlabeled org. Exceeds schema detail.

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 'Create an empty organization on the prototype tier' with specific HTTP method and endpoint, and notes the user becomes owner. Distinguishes from siblings like list_orgs, rename_org.

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: optional display_name, no tier at create, separate flow for paid tiers, and step-up gating with cap limit error. Lacks explicit when-not-to-use but implies through constraints.

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