list_activities

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

The description lacks any behavioral details such as pagination, filtering, ordering, authentication requirements, or output format. With no annotations provided, the description carries the full burden and fails to convey essential runtime behavior.

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 very short (one sentence), which is concise, but it is overly minimal and lacks structure. It could be improved by front-loading key details while remaining efficient.

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 the complexity of the parameter set and the existence of many sibling tools, the description is incomplete. It does not mention pagination, filtering, or the output schema (which exists but is undocumented in the description), leaving the agent with insufficient context.

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%, and the description adds no information about the parameters (page, page_size, starts_on_or_after). An agent must infer meaning from parameter names alone, which is insufficient for correct invocation.

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 ('List') and resource ('timesheet activities'), making the basic purpose unambiguous. However, it does not differentiate from sibling tools like list_activity_categories, which may cover similar domains.

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 guidance is provided on when to use this tool versus the many sibling list tools (e.g., list_activity_categories, list_appointments). The description offers no context for selection criteria or prerequisites.

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