update_organisation_defaults

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

Beyond the annotations (idempotentHint, readOnlyHint=false), the description discloses immediate enforcement propagation, partial-update behavior, required API key scope, Enterprise gating, and the 403 error on non-Enterprise plans. This adds substantial operational context that annotations alone do not convey. No contradictions with annotations.

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 compact—four sentences—with each sentence earning its place: function, behavior, safety, permissions, and error handling. It is front-loaded with the core purpose and avoids redundancy or filler.

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 moderately complex mutation tool, the description covers all essential aspects: what it does, how it behaves (immediate propagation), prerequisites (inspect read tools), idempotency, authentication, and error condition. The existence of an output schema also covers return values. No significant gaps remain.

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 baseline is 3. The description adds meaningful semantics by stating "Only supplied directions change," clarifying that parameters are optional and act as partial updates. This is extra value beyond the schema descriptions, warranting a slightly higher score.

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 opens with a specific verb "Replace" and clearly identifies the resource: "organisation-wide default input and/or output guardrail lists inherited by workspaces." It distinguishes itself from sibling tools like update_input_guardrail_workspace_exclusions and update_output_guardrail_workspace_exclusions by focusing on the defaults rather than exclusions.

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 instructs the agent to "inspect get_organisation_defaults and the directional workspace exclusions first," providing clear prerequisite steps. It also notes that only supplied directions change and that repetition is safe, giving practical usage context. It stops short of explicitly naming alternatives or when-not-to-use scenarios, but the guidance is solid.

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