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

With no annotations, the description must disclose behavior on its own. It notes that it returns the updated organization summary and explains instance targeting. However, it does not mention permissions, partial vs. full updates, potential side effects, or error conditions. It is adequate but not thorough 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?

The description is four concise sentences, front-loaded with the purpose, and includes only useful operational notes (prerequisite, targeting, return value, cost). No redundancy or fluff. 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?

The description provides essential context (prerequisite call, targeting, return type) but misses differentiation from the sibling update_organization_metadata tool, which overlaps on metadata fields. It does not clarify whether fields are merged or replaced, though the schema hints at merge. Given the output schema and schema param coverage, the description is moderately complete.

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%, so the baseline is 3. The description repeats the guidance for clerk_instance_id that already exists in the schema, adding no new semantic value beyond what the schema provides. Other parameters are self-explanatory.

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 states 'Update fields for a Clerk organization' with a clear verb and resource. It does not explicitly distinguish from sibling tools like update_organization_metadata, but the scope is understandable. The name and description align, making the purpose reasonably clear.

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 gives explicit usage context: 'Call clerk.get_connected_accounts first' and explains how to target a specific connection or use the default. It lacks explicit alternatives or exclusions (e.g., when to use create_organization instead), but the guidance is actionable and relevant.

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