Collaborator: Edit Remote System Configuration

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

The description states 'Edits parameters', a write operation, but the annotations set readOnlyHint to true. This is a direct contradiction. Additionally, the description does not disclose any other behavioral traits such as required permissions or side effects, leaving the agent with inconsistent information.

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 concise with one primary sentence and a bullet list of parameters. However, the parameter list is redundant with the input schema and the toolset line adds minimal value. It is front-loaded with the action but contains some unnecessary repetition.

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 the tool has 4 parameters, no output schema, and annotations that include a contradiction, the description fails to provide sufficient context. It does not explain return values, side effects, or resolve the inconsistency about which fields are editable. The contradiction with both annotations and schema leaves the agent underinformed.

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?

While the schema coverage is 100%, the description adds the constraint that only title and config are editable, which contradicts the schema's inclusion of reviewTemplateId as a parameter. This creates confusion rather than adding value. The parameter descriptions in the description simply mirror the schema without deeper explanation.

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 verb 'Edits' and the resource 'existing remote system configuration' in Collaborator. It distinguishes this tool from siblings like create, delete, test, and webhook update by specifying that it edits parameters after creation.

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?

The description mentions that only title and config are editable after creation, but the input schema also includes reviewTemplateId as an editable parameter. This contradiction provides misleading guidance on when to use this tool versus alternatives like recreating the configuration.

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