task_events

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

The description discloses automatic payload truncation, a key behavioral trait. However, it does not mention auth requirements, read-only nature, or behavior when task_id is null. With no annotations, more disclosure would be beneficial.

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 three sentences, front-loaded with purpose, and every sentence adds value. No redundant or missing information.

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 lack of output schema and annotations, the description is adequate for basic usage but lacks details on return format, error handling, and behavior with missing parameters. It covers the main functionality but is not exhaustive.

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 0% parameter descriptions, so the description must compensate. It explains include_payload's effect, but task_id, limit, and offset are only implied by names. This provides marginal value beyond the 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 'Fetch paginated execution events for a task,' which is a specific verb and resource. It distinguishes from siblings like task_get and task_list by focusing on events rather than task details or listing.

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?

The description advises using include_payload=True for full data and mentions truncation, but does not explicitly state when to use this tool versus siblings like task_get or task_list. No prerequisites or when-not conditions are provided.

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