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

Annotations declare the safety profile (non-read-only, non-destructive), so the description's job is limited to adding context, and it does: it discloses that turning this on injects the organization profile into the agent's instructions at run time and that the initial state is off. It stops short of stating whether a republish/rebuild is required for the change to take effect or what permissions are needed.

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 short sentences, front-loaded with the action and immediately followed by the effect and default state. No filler and nothing to trim.

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 two-parameter toggle with full schema coverage, annotations, and no output schema, the description covers what changes, when it applies, and the default. Only minor gaps remain, such as whether the change takes effect immediately and how to read back the current state.

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 a genuine semantic detail beyond the schema by stating the setting is off by default, which tells the agent the meaning of the current state. The boolean semantics of 'enabled' are still largely carried by the schema.

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 names a precise action (turn a named setting on or off) and explains the substantive effect: the organization profile is appended to the agent's instructions at run time. That is far more than a restatement of the title. It does not explicitly contrast itself with nearby siblings like set_governance_policies or set_triggers, so a 5 is withheld.

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 useful context (off by default, affects the agent only at run time) but offers no explicit when-to-use trigger, no prerequisites, and no named alternative for achieving similar behavior. Usage is implied rather than directed.

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