add_gear_to_activity

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

There are no annotations, so the description carries the full behavioral burden. It discloses the core mutation (linking gear to an activity), but it does not mention side effects, duplicate association behavior, whether existing associations are replaced, error conditions, or permission requirements. For a mutation tool with no safety annotations, this is a meaningful gap.

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 short and front-loaded with the action, followed by a clear Args section. The first two sentences are somewhat redundant, but overall every remaining part earns its place and the structure is easy to parse.

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 two-parameter tool, the description covers the essential purpose and arguments. However, with no annotations, it omits behavioral details such as idempotency, duplicate handling, and prerequisite conditions, and it does not explicitly route the agent to related tools like remove_gear_from_activity. It is adequate but leaves some gaps.

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 0%, and the description fully compensates by explaining both parameters in plain language. It also adds the helpful detail that gear_uuid should come from get_gear, which goes beyond the schema's bare type information.

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 operation: 'Associate gear with an activity' and 'Links a specific piece of gear (like shoes, bike, etc.) to an activity.' It uses a specific verb and resource, and distinguishes itself from siblings like remove_gear_from_activity and get_activity_gear by making the add/link intent explicit.

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 makes the use case clear—attach a specific gear item to an activity—and even tells the agent to get the gear_uuid from get_gear. It does not explicitly contrast with remove_gear_from_activity or state exclusions, but no sibling performs the same add operation, so the guidance is sufficient.

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