add_activities

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

With no annotations, the description carries the full burden of disclosing side effects. It merely says 'Add new activities to Daily' without mentioning that setting archiveExistingActivities=true will archive existing activities, potentially replacing the current list. This important behavioral trait is only visible in the schema, not the description.

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 a single concise sentence that front-loads the action and object. It contains no filler or redundant text, earning a maximum score for brevity and structure.

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's mutation nature, no output schema, and no annotations, the description is incomplete. It fails to explain the impact of the archive flag, the expected response, or any prerequisites. This makes the tool only minimally documented for effective 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 description coverage is 100% for both parameters, so the baseline is 3. The description itself adds no parameter-level detail, but the schema already provides sufficient information about the activities array and archiveExistingActivities flag.

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 ('Add'), the resource ('activities'), and the destination ('Daily'), making it obvious this is a write operation distinct from the sibling get_* tools. However, it does not explicitly differentiate itself from other add/update tools or mention the bulk/archive behavior, which the schema implies.

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?

No guidance is provided on when to use this tool vs alternatives. The description lacks prerequisites, context, or any note about using get_activities to review existing activities before adding. The 'Add' verb vs get_ siblings is the only implicit usage signal.

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