cortex_update_organization

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

No annotations exist, so the description must disclose behavior. It accurately states that only description or status can be updated and that superadmin key is needed. However, it does not mention if the update is partial (e.g., other fields preserved) or what the response indicates.

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, front-loaded sentence with no extraneous words. Every element (verb, resource, fields, auth requirement) is essential and immediately informative.

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 update tool with no output schema, the description covers the essential operation and auth requirement. However, it does not mention the return value (e.g., updated organization object) or error conditions (e.g., invalid orgId, permissions).

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 coverage is 100%, so the schema already describes each parameter. The description adds no extra semantics beyond indicating that status accepts 'Active' or 'Locked' (already in schema enum). It provides minimal added value 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?

The description clearly states 'Update an organization's description or status', specifying the verb 'Update', the resource 'organization', and the exact fields modifiable. This distinguishes it from sibling tools like cortex_create_organization (create) and cortex_get_organization (read).

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 includes 'requires superadmin API key', giving a clear prerequisite for usage. It does not explicitly list when not to use or specify alternatives, but the purpose is narrowly defined, and the auth hint aids selection.

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