List activities

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions ISO 8601 format but omits critical details like pagination behavior, data volume, ordering, rate limits, or whether the tool is read-only. The schema reveals pagination parameters but the description does not explain the cursoring mechanism.

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?

Two focused sentences with no wasted words. The structure is logical: action first, then format clarification. Could be improved by integrating more behavioral info without sacrificing conciseness.

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 7 parameters (including optional filters and pagination), no output schema, and no annotations, the description should cover pagination, ordering, result format, and usage constraints. It fails to address these, leaving significant gaps for an AI agent to invoke correctly.

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 100%, so baseline is 3. The description adds the ISO 8601 format hint, which is already present in the schema descriptions for the time parameters. Minimal added value beyond schema.

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 tool lists tracked time activities for an organization within a time range, using specific verbs and resources. It distinguishes the tool from siblings like hubstaff_daily_activities by implying a more granular time-based listing, but does not explicitly differentiate.

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 on when to use this tool versus alternatives (e.g., hubstaff_daily_activities) or when not to use it. The description provides no context on prerequisites, exclusion criteria, or recommended scenarios.

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