Create Activity

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

Annotations already set destructiveHint to false, indicating non-destructive behavior. The description adds no extra behavioral context beyond the fact that it creates an activity, such as permissions or side effects. Since it does not contradict annotations, a score of 2 is warranted.

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 short sentence that is front-loaded and efficient. It is not overly verbose, but could be slightly more informative without becoming wordy.

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 that all parameters are well-documented in the schema and there is no output schema, the description is adequate. The parenthetical '(project)' adds helpful context to disambiguate from other activity types. However, it does not mention return behavior or post-creation steps.

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%, so the baseline is 3. The description does not add additional meaning beyond what the schema already provides for each parameter.

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 'Create a new activity (project)', using a specific verb and resource. It distinguishes from sibling tools like update_activity or archive_activity by focusing on creation.

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 creation context but provides no explicit guidance on when to use this tool versus alternatives like update_activity or list_activities. There are no when-not or exclusion criteria mentioned.

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