create_activity

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

With no annotations, the description carries the full burden. It usefully discloses that the resource is flat (no milestones/hierarchy) and which fields are mandatory, but says nothing about permissions, whether the created activity is returned, duplicate/validation behavior, or any rate limits.

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?

Three tight sentences, front-loaded with the action and the most surprising constraint (flat list), then requirements, then the status-ID prerequisite. No filler to cut.

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 an 11-parameter mutation with no output schema, the description covers required fields, the notable unsupported-shape trap, and the status-ID discovery path. It is nearly complete, missing only return-value expectations and failure/permission behavior.

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 coverage is 100%, so each parameter including the 'NOT SUPPORTED' KindId/ParentId notes is already documented in the schema. The description largely restates required-field and status-lookup facts the schema already encodes, adding little new syntax or format detail.

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?

States a specific verb and resource ('Create a new activity in a service') and immediately scopes it by noting activities are a flat list with no hierarchy. It implies but never explicitly states the distinction from the sibling create_task, which is the main confusion risk.

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?

Gives concrete prerequisite guidance: activity statuses differ from task statuses and valid IDs must be discovered via get_reference_data with entity "activitystatuses". It does not state when an agent should choose create_activity over create_task/create_project, so it stops short of full routing guidance.

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