patchGlobalEnumeration

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

Annotations are absent, so description must convey all behavioral traits. Only says 'Updates' without specifying partial update semantics (PATCH), required permissions, or effects of missing enumerations. No side effects or constraints disclosed.

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?

Single sentence, front-loaded with verb and resource. Efficient but omits useful context; loses a point for being too terse given tool complexity.

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?

Tool has nested requestBody and no output schema. Description does not mention required structure of requestBody, no guidance on id or attributes, and no return value info. Insufficient for a complex mutation 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. Description adds minor value via enumContext allowed values hint, but does not explain requestBody structure or usage beyond 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?

Description clearly states the tool updates a specific resource (Enumeration) in a specific context (Global). This distinguishes it from sibling tools like patchProjectEnumeration or deleteGlobalEnumeration by specifying 'Global 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 on when to use this tool versus alternatives (e.g., postGlobalEnumeration for creation, patchProjectEnumeration for project enums). No scenario or prerequisites mentioned.

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