list_aoc_task_events

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

The description implies a read-only operation via 'List', but does not disclose ordering, pagination, limits, or side effects. With no annotations, the agent must infer safety. The verb itself is strong, but no additional context is provided.

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?

A single sentence that is efficient and front-loaded. No wasteful words, but the lack of structure (e.g., bullet points) is acceptable for such a simple 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 simple input schema and presence of an output schema, the description covers the essential purpose. However, it omits prerequisites (e.g., task must exist) and potential filters. It is minimally viable but not comprehensive.

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 sole parameter 'task_id' has no schema description (0% coverage). The tool description mentions 'against an AutoCompany task', hinting at the parameter's role, but does not explain format, how to obtain it, or validation. More detail is needed.

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 uses 'List events recorded against an AutoCompany task' which clearly indicates the action and resource. It distinguishes from sibling 'list_aoc_tasks' (lists tasks) and 'post_aoc_task_event' (creates events), though it does not explicitly differentiate from other list tools.

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. The description does not mention prerequisites, context for optimal use, or exclude cases (e.g., 'use this to retrieve events, not to create them').

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