Remove Gear from Activity

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

The description aligns with the destructiveHint annotation, confirming it is a destructive operation. It does not add extra behavioral details beyond the annotation, but consistency with the annotation satisfies the lower bar for transparency when annotations are present.

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 highly concise, consisting of two clear sentences with no redundant information. It efficiently conveys the action and a necessary prerequisite.

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?

The description covers the core action and a practical note about obtaining the required UUID. Since there is no output schema, no return value explanation is needed. It is sufficiently complete for a simple unlink operation, though it could optionally mention reversibility or effects.

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?

The input schema already provides detailed descriptions for both required parameters (gearUUID and activityId), including how to obtain the gear UUID. The tool description adds no new information about parameters, so it does not contribute beyond the schema's high coverage.

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: 'Remove/unlink a piece of gear from an activity.' It uses a specific verb and resource, distinguishing it from sibling tools like 'link_gear_to_activity' and 'delete_gear'.

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 does not explicitly state when to use this tool versus alternatives or provide excluding conditions. The purpose is implied, but no direct guidance on when to prefer this over other gear-related operations is given.

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