icu_bulk_create_manual_activities

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

The description discloses key behavioral traits beyond annotations: the UPSERT logic (updating existing records), the condition of matching external_id within the same OAuth app, and the exclusion of device uploads. Annotations already mark it as destructive and non-readOnly, but the description explains the specific destructive mechanism and auth scope.

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 two sentences, front-loaded with the core purpose and then elaborating on behavior. Every sentence adds value without redundancy. No filler or unnecessary words.

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 presence of output schema and annotations, the description covers the essential behavioral contract: upsert logic, manual-only scope, and OAuth app restriction. It could mention error handling or batch size limits, but is mostly complete for practical use.

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 coverage is 100%, but the description adds significant meaning: it explains that activities_json contains the external_id field for upsert matching, and clarifies athlete_id is for coaches. This goes beyond the schema descriptions, which only name the 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 tool performs batch creation of manual activities with UPSERT behavior, and distinguishes itself by specifying 'no device upload' and the unique upsert-on-external_id mechanism. This differentiates it from siblings like icu_bulk_create_events and individual activity tools.

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 explains the upsert behavior and OAuth app constraint, providing clear context for when to use this tool (for batch manual activity management with external_id matching). However, it does not explicitly state when not to use it or mention alternatives, such as individual create/update tools.

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