list_time_entry_activities

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

With no annotations provided, the description carries full responsibility for disclosing behavior. 'List' clearly implies a non-destructive read operation, but it does not mention output format, ordering, or access requirements. This is acceptable for a likely simple list operation, but lacks contextual depth.

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, concise sentence that fully states the tool's purpose. Every word earns its place, and there is no unnecessary elaboration. This is appropriate for a zero-parameter listing tool.

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 low complexity (zero parameters, no nested objects, no output schema), the description is adequately complete for a simple list action. It could mention what the returned activities look like, but for the apparent simplicity of the tool, the current description suffices.

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 schema has zero parameters, so the baseline is 4. The description does not need to explain any parameters, and it correctly refrains from adding misleading syntactic details. The term 'available' adds slight semantic value about the scope of the list.

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 'List available time entry activities' uses a specific verb ('List') and a clear resource ('time entry activities'), making its purpose immediately understandable. It distinguishes itself from sibling tools like list_time_entries and list_categories by naming a distinct resource, though it relies on the tool name for full differentiation.

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. There are no mentions of prerequisites, typical scenarios, or exclusions. The description simply states what it does, leaving the agent to infer usage from the name and sibling context.

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