manus_task_list_messages

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

Describes cursor pagination and the effect of verbose=true on event types. With no annotations, the description adds some behavioral insight but omits details like permissions, error behavior, or rate limits.

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 sentences with no redundancy. Front-loaded with the primary action, but no bullet points or structure for easier scanning.

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 6 parameters, no output schema, and no parameter descriptions in the schema, the description leaves major gaps: return format, pagination details, meaning of slides_format, and event structure.

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?

With 0% schema description coverage, the description explains only the verbose parameter and implicitly cursor/limit through 'cursor pagination'. It lacks explanations for task_id, order, slides_format, and cursor/limit specifics.

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?

Clearly states it lists task events with cursor pagination. The verb 'List' and resource 'task events' are specific. Uniqueness among siblings is implied but not explicitly stated.

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?

Provides usage guidance for the verbose parameter and hints at inspecting status_update events. However, it does not specify when not to use this tool or suggest alternatives.

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