update_organisation_defaults

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

Goes well beyond the annotations: it discloses partial-update semantics (only supplied directions change), immediate org-wide propagation to non-excluded workspaces, required API key scope (organisation_settings.update), Enterprise gating, and the exact 403 failure mode. The "repeating the same lists is safe" line reinforces idempotentHint with operational meaning.

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?

Three sentences, front-loaded with the action, then preconditions, then auth/gating. No filler; each clause carries either a precondition, a side effect, or a failure mode.

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?

An output schema exists so return values needn't be described, and everything an agent needs to call correctly is present: prep steps, mutation semantics, propagation scope, credential scope, and an explicit error condition.

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% and both parameters carry ordering/type documentation, so the baseline is 3. The description adds one genuinely new semantic — that omitted directions are left untouched — which is the key behavioral fact about the two optional array parameters.

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?

"Replace the organisation-wide default input and/or output guardrail lists inherited by workspaces" names a specific verb (replace), the exact resource (org-level defaults), and the inheritance scope. It is clearly separable from the per-direction exclusion siblings and from update_guardrail (individual guardrail edits).

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?

It gives concrete sequencing guidance — inspect get_organisation_defaults and the directional workspace exclusions before calling — which tells the agent how to prepare. It stops short of explicitly routing the agent to a different tool when the intent is per-workspace scoping (update_input/output_guardrail_workspace_exclusions), so the alternative-selection logic is only implied.

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