set_activity_name

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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals that the operation mutates an activity's name but does not mention overwrite behavior, side effects, permissions, idempotency, or what happens if the activity does not exist.

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 appropriately sized: a single front-loaded purpose sentence followed by a minimal Args list. Every sentence adds value and the structure is easy to scan.

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?

This is a simple two-parameter setter, and the description supplies enough information for an agent to call it correctly: what it does and what each parameter means. The output schema exists but is not shown; the description would benefit from a note about return behavior, but this is not critical for such a straightforward operation.

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 Args section provides meaningful descriptions for both parameters, clarifying that activity_id identifies the activity to update and activity_name is the new name. This goes beyond the schema, which only provides field names, and fully compensates for the 0% schema description 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 a specific action ('Set or update') and resource ('the name of an activity'), which distinguishes it from sibling setters like set_activity_type and set_activity_description. The one-line summary is unambiguous.

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 implies when to use this tool: when an activity's name needs to be set or changed. However, it does not explicitly mention alternatives or state when not to use it, leaving sibling differentiation to inference from the tool name.

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