Collaborator: Update Remote System Configuration Webhook

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

The description says 'Updates the webhook,' which is a write operation, while the annotations declare readOnlyHint: true. This directly contradicts the annotation and could cause an agent to treat this as a non-mutating call. No additional behavioral context is provided beyond the conflicting action verb.

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 opening sentence is clear and front-loaded, but the description includes a 'Parameters:' block that duplicates the schema verbatim. The 'Toolset' line adds mild context, so the description is short but contains redundant content.

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 mutation tool with one parameter and no output schema, the description provides the minimum callable information. However, it leaves the annotation contradiction unaddressed and omits any detail about the webhook payload, required permissions, or response, making it insufficient for fully reliable invocation.

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 description coverage is 100%, and the description repeats the id parameter's purpose without adding new details such as ID format, source, or prerequisites. The baseline of 3 applies because the schema already fully documents the parameter.

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?

States a specific verb and resource: 'Updates the webhook for a remote system configuration in Collaborator by its ID.' This distinguishes it from sibling configuration-management tools like collaborator_edit_remote_system_configuration, though it does not clarify what webhook fields can be updated.

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 such as collaborator_edit_remote_system_configuration or webhook-related operations. There are no prerequisites, exclusions, or conditions that would help an agent choose between this and competing tools.

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