REP Helper

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

With no annotations provided, the description carries the full burden. It explains the partial update behavior well but fails to disclose safety characteristics (is it destructive? atomic?), return values, or constraints like the max 3 trips/files limit mentioned in the schema. The 'remove existing evidence' hint suggests destructive capability but doesn't classify it.

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?

Three sentences with zero waste: purpose statement first, update semantics second, specific capabilities third. Every word earns its place. Front-loaded structure makes it immediately scannable.

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 complex 16-parameter mutation tool with file handling and relationships, the description covers the essential mechanics but is incomplete regarding return values (no output schema exists) and error conditions. The 100% schema coverage compensates somewhat, but behavioral gaps remain given the lack of annotations.

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?

Despite 100% schema description coverage (baseline 3), the description adds significant value by explaining the partial update semantic ('Only include fields you want to change') that applies to all optional parameters. It also usefully aggregates related operations (evidence attachment/removal) that are spread across multiple parameters.

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 (update) and resource (activity), specifying it works on 'existing' activities which distinguishes it from create_activity. It lists specific capabilities (trips, evidence files) that clarify the scope beyond a generic update.

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 provides crucial guidance on partial updates ('Only include fields you want to change'), indicating PATCH-like semantics. However, it lacks explicit guidance on when to use this versus create_activity or delete_activity, and doesn't mention prerequisites like requiring a valid activity ID.

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