cortex_create_organization

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

With no annotations, the description carries the burden of behavioral disclosure. It correctly notes the need for a superadmin API key, which is a critical auth requirement. It does not mention idempotency or uniqueness constraints, but the 'create' verb implies a new resource is always created.

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 that is front-loaded with the action and resource. Every word is necessary, with no extraneous information.

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 two required parameters and no output schema, the description covers the key points: action, resource, and auth requirement. It could optionally mention the return value (e.g., the created organization object) but this is not essential.

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?

The input schema has 100% coverage with descriptions for both parameters ('name' and 'description'). The description does not add additional meaning beyond the schema, so it meets the baseline for high coverage without exceeding it.

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 action ('Create') and resource ('organization'), and distinguishes from sibling tools like cortex_update_organization and cortex_list_organizations. The requirement for a superadmin API key adds specificity.

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 context by noting the superadmin API key requirement, which guides when to use the tool. However, it does not explicitly mention when not to use it or contrast with alternatives like cortex_update_organization, though the verb 'create' implies it's for initial creation.

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