update_organization

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

Discloses update mutation and array clearing behavior. With no annotations, more detail on side effects, validation, or permissions would improve transparency for a mutation tool.

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 redundancy. Purpose is front-loaded, with additional guidance in a concise manner. Every sentence earns its place.

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 key usage aspects. No output schema, but description focuses on input behavior. Could mention response details, but not essential for a well-understood update operation.

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?

All 6 parameters have schema descriptions (100% coverage). The description adds value beyond schema by explaining partial updates and array clearing, aiding correct parameter usage.

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?

Description clearly states it updates an existing organization, distinguishing it from create_organization and delete_organization. The verb 'update' and resource 'organization' provide a specific and unambiguous purpose.

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?

Explicitly advises to pass only fields to change, which is a typical PATCH behavior. Also provides special guidance for clearing array fields. However, no comparison to alternative tools like create_organization or get_organization.

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