Collaborator: Delete Remote System Configuration

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

The description says 'deletes', which implies a destructive write operation, but annotations set readOnlyHint=true and destructiveHint=false. This is a direct contradiction that misleads the agent about the tool's safety profile.

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 concise, with only two sentences and no unnecessary words. It is front-loaded with the essential action.

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 simple deletion tool with one parameter and no output schema, the description offers minimum viable information. However, the annotation contradiction undermines completeness and could cause the agent to misbehave.

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?

Only one parameter (id) with schema description covering 100% of the parameters. The description repeats the schema's parameter description without adding new semantic value. Baseline score applies.

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 clearly states the action ('Deletes'), the resource ('remote system configuration'), and the mechanism ('by its ID'). It distinguishes this tool from sibling tools like collaborator_create_remote_system_configuration and collaborator_edit_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?

No guidance on when to use this tool versus alternatives, prerequisites, or post-conditions. The description only states the action without contextual advice.

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