accelo_list_thread_activities

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

With no annotations, the description carries the full behavioral burden. Read-only behavior is only implied by 'List', and there is no statement about pagination totals, ordering, permissions, or result shape for a 4-param list operation.

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 purpose sentence is front-loaded and the per-argument notes are terse and information-dense with no filler. Structure is a clean purpose line plus Args list, appropriate for its size.

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 list tool with no output schema and no annotations, the description covers inputs well but says nothing about what comes back (fields available, total count, ordering) or how the thread results relate to the parent activity. Adequate but with clear gaps.

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 0%, so the description must compensate, and it largely does: it defines thread_id as the activity_id of the original activity, gives an example value for fields, and states that page is 0-indexed and limit is capped at 100. These details go beyond the bare schema titles.

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 (List), resource (activities) and scope (within a single thread), which distinguishes it from the broader accelo_list_activities and from accelo_list_activity_threads. It does not explicitly name those siblings, so the agent must infer the boundary from scope wording alone.

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 is given. The agent can infer that it should call this to expand a thread, but nothing states how this differs from accelo_list_activities or when a thread_id is the right key to start from.

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