start_activity

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

No annotations provided, and the description only describes the action without disclosing side effects, permissions, or behavior (e.g., whether it triggers notifications, other side effects).

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 structured as a docstring with a clear first sentence and parameter list. While somewhat verbose by repeating schema info, it is necessary because the schema lacks descriptions.

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?

All parameters are explained, but the description does not mention what the tool returns (output schema exists but not described) or behavioral context like whether it's blocking or part of a workflow.

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 description adds meaningful explanations for each parameter (e.g., 'title to show when the activity starts'), which is lacking in the input schema (0% coverage). It also notes defaults and optionality.

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 'Start' and the resource 'an activity', and it distinguishes from sibling tools (end_activity, update_activity, send_notifications) by implying this is for initiating, not ending or updating.

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 on when to use this tool versus alternatives, no prerequisites or context for its invocation.

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