set_activity_type

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds only that the call returns null on success and can be verified via getActivity, but says nothing about what existing type assignment is overwritten, whether typeId/typeKey/parentTypeId must be consistent, or permission requirements.

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?

It is short, but the space is spent on a return-value aside rather than the tool's purpose, so it is under-specified rather than concise. Nothing is front-loaded because the core action is never stated.

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 four-parameter mutation with 25% schema coverage, no output schema, and no parameter documentation, the description is inadequate. It does not tell an agent what the tool changes or how to build a valid call.

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 only 25% — three of four required parameters (typeId, typeKey, parentTypeId) have no schema descriptions at all, and the description adds zero parameter meaning. The relationship between typeId, typeKey, and parentTypeId is completely undocumented.

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 never states what the tool does. It opens with a fragment about the return value ('resolves to `null` on success') and a verification note, leaving the actual purpose (assigning an activity type to an activity) to be inferred entirely from the name and sibling set.

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?

There is no when-to-use guidance, no distinction from near-siblings such as set_activity_event_type or set_activity_name, and no mention of prerequisites like valid typeId/typeKey values. Usage is only implied by the tool name.

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