accelo_create_activity

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the medium default ('note') and marks three required fields, but says nothing about permissions needed, visibility of the created activity, side effects, or what happens with an invalid against_type. For a mutation tool with zero annotation coverage this is a real gap.

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 one-line purpose is front-loaded and the Args list is compact, one line per parameter. A few lines (priority_id, class_id, owner_id) restate their names without adding value, which is minor waste but not bloat.

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 12-parameter mutation tool with no annotations and no output schema, the description covers parameters adequately but leaves behavioral context thin: no auth/permission requirements, no note on what the created activity returns or its side effects. It is complete on the argument surface but incomplete on 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?

With 0% schema description coverage, the description is the only documentation, and it documents all 12 parameters. It adds genuine meaning for several: against_type examples (company, job, issue, staff, task), owner_type options ('staff' or 'affiliation'), medium enum values and default, and the unit for billable/nonbillable ('seconds'). A few entries are tautological (priority_id: Priority ID, class_id: Activity class ID), which keeps it from a 5.

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') and enumerates the subtypes it covers (note, email, call, meeting), which helps distinguish it from siblings like accelo_create_task or accelo_create_expense. It does not explicitly contrast itself with accelo_update_activity or accelo_convert_time_external_to_activity, so it stops short of full sibling differentiation.

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 when-to-use or when-not-to-use guidance. There is no statement about choosing this over accelo_create_task/accelo_create_issue, nor about prerequisites such as needing a valid against_type/against_id before calling. The medium default hints at usage but that is schema-level detail, not routing guidance.

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