update_org_policy

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

No annotations are provided, so the description carries full burden. It only says 'update', implying mutation, but does not disclose side effects, required permissions (e.g., admin rights), request limitations, or the impact of the data parameter. This is insufficient for safe autonomous use.

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 extremely short (3 words) and omits critical context. While conciseness is positive, it sacrifices necessary detail for safe tool invocation, making it under-specified.

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?

Given 3 parameters including a nested object (data) and no output schema, the description lacks essential context about how data is used, whether the policy must already exist, and what happens on update. The tool's role in the org policy lifecycle is unclear.

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?

The input schema has 100% description coverage, with clear parameter definitions (policyType as enum-like integer, enabled boolean, data object). The description adds no additional meaning beyond the schema, which already explains the parameters well. Baseline score of 3 is appropriate.

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 a policy' which clearly identifies the verb (update) and a generic resource (policy). However, it does not specify that this is for organization policies, nor does it distinguish it from sibling tools like update_org_collection or get_org_policy. The resource is vague without the name context.

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?

No guidance is provided on when to use this tool versus alternatives. Siblings include get_org_policy and list_org_policies, but there is no suggestion to retrieve first before updating, or any mention of prerequisites or exclusions.

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