accelo_convert_time_external_to_activity

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

With no annotations, the description carries the full burden, and it does disclose a non-obvious behavior: two activities are created (a meeting plus a report on the meeting). It does not state what happens to the source time external (deleted, mutated, or left intact), whether the operation is idempotent or reversible, or what permissions are required — significant gaps for a mutation tool with zero annotation coverage.

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 core purpose and the two-activity behavior are front-loaded in the first two sentences, with parameter detail relegated to a clearly labeled Args block. It is slightly verbose in restating 'against_type'/'against_id' alongside the parameter names, but every line carries information.

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 three-parameter mutation tool with no annotations and no output schema, the description covers purpose, the surprising multi-record side effect, and all three parameters with domain context. It stops short of describing error conditions or the fate of the source record, which an agent would need for full confidence.

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 0%, so the description must compensate, and it does: it maps each parameter to a domain meaning ('Time External ID', 'the against_type ... e.g. company, job, issue', 'the against_id — ID of the object to create against'). The example values for engagement_table are especially useful since the schema provides no enum or description for it.

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 first sentence names a specific verb and resource ('Convert a time external ... into an activity') and the second clarifies the exact side effect (a meeting activity plus a report activity). This clearly distinguishes it from generic siblings like accelo_create_activity or accelo_update_activity, which would otherwise look interchangeable.

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?

It implies context by describing the operation as 'the process for turning an imported appointment into a workable Accelo timesheet/schedule entry,' which suggests when it applies. However, it gives no explicit when-to-use guidance, no prerequisites (e.g. that the time external must first be found via accelo_list_time_externals), and no statement of when NOT to use it versus creating an activity directly.

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