create_org

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

No annotations, but description discloses error condition (FREE_ORG_OWNER_LIMIT_EXCEEDED), response fields, and ownership. Could add auth or idempotency details but sufficient.

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?

Single sentence packed with all necessary information, well-structured with semicolons, no redundancy.

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?

Covers main action, parameter, response fields, and constraints. With no output schema, additional details like return format could help, but current is 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?

Adds significant value beyond schema: clarifies that display_name is optional, non-unique, not an id, and that tier is not an input. Includes example.

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 the action (create), resource (organization), and specifics (empty, prototype tier, ownership). Distinguishes from siblings like rename_org or set_tier.

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?

Mentions step-up gating, free-org cap, and that tier is not input but reported. Provides clear context for when to use, but lacks explicit when-not or alternatives.

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