Collaborator: Delete Remote System Configuration

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

The description states the tool 'Deletes' a configuration, which is a mutating and destructive operation, but the annotations declare readOnlyHint=true and destructiveHint=false. This is a direct contradiction that makes the tool's actual behavior unreliable for an agent.

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 core action is stated in one clear, front-loaded sentence. The additional Toolset and Parameters blocks are somewhat redundant with the structured data but do not make the description excessively long.

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?

Even though the tool has only one parameter, the description omits important behavioral context such as whether deletion is reversible, what happens to dependent data, or required permissions. The annotations further mislabel the operation as read-only, making the overall definition unreliable.

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 merely repeats the schema text: 'ID of the remote system Configuration to delete.' The parameter is already fully documented in the schema, so the description adds little semantic value.

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 uses a specific verb 'Deletes' and identifies the exact resource, 'remote system configuration in Collaborator', with the key selector 'by its ID'. This clearly differentiates it from sibling tools like create, edit, or test remote system configuration.

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?

There is no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The 'Toolset' label only names a category without explaining when deletion is appropriate.

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