list_job_activities

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

With no annotations provided, the description carries the full burden. It specifies the HTTP method (GET) and tier (readonly-owner), indicating a safe read operation, but does not describe pagination, rate limits, or any side effects. The information is adequate but minimal.

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 a single sentence plus endpoint and tier note, with no redundancy or unnecessary words. It is front-loaded with the core action and resource.

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?

The description is adequate for a simple list tool with a well-documented schema. However, it lacks guidance on output format (no output schema) and does not differentiate from the sibling get_job_activity. Additional context about when to paginate or use filters would improve completeness.

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?

The input schema provides 100% coverage with detailed descriptions for both parameters (cursor and filter). The description adds no new semantic information beyond 'optionally filtered', which aligns with the schema. Baseline of 3 is appropriate given the schema richness.

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 verb 'List' and the resource 'scheduled booking or recorded time entry on a job records', which is interpretable as job activities. It also mentions optional filtering and the HTTP endpoint, distinguishing it from the singular get_job_activity sibling. However, phrasing is slightly awkward and could be more precise.

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 alternatives like get_job_activity or other list tools. There is no mention of prerequisites, limitations, or context where other tools would be better suited.

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