Set Object Schema Column Active State

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

Annotations provide readOnlyHint: false, destructiveHint: false, idempotentHint: false. The description adds value by clarifying that deactivate is a 'soft-disable' that is reversible and does not delete the column, and that reactivate restores it. This context goes beyond annotations, though it could mention potential side effects or required permissions.

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 concise sentences that efficiently convey the purpose and the two operations. No wasted words, front-loaded with key 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?

With 4 parameters and no output schema, the description covers the action parameter's semantics well. It could provide more context on how to obtain columnId or object schema IDs (e.g., from other tools), but the sibling list includes relevant tools, so overall it is sufficiently complete for a state toggle tool.

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 baseline is 3. The description restates information from the schema (e.g., action enum descriptions), but does not add significant new meaning beyond what the schema already provides.

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 explicitly states the tool's purpose: 'Set the active state of a column on an account-level object schema.' It further distinguishes the two actions (deactivate and reactivate) and their effects, clearly differentiating from sibling tools like manage_object_schema_columns.

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 explains when to use each action (deactivate to soft-disable, reactivate to restore), but it does not provide explicit guidance on when not to use this tool or mention alternatives from the sibling list, such as manage_object_schema_columns for broader column management.

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