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

Annotations already establish that this is safe and read-only. The description adds value by specifying the exact returned fields (title, type, status, due date, assigned contact id), which matters because there is no output schema. It does not mention pagination or ordering, but these are minor for a simple list operation.

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?

One tight, front-loaded sentence states the action, scope, and result fields without filler. Every phrase contributes to tool selection and invocation.

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?

For a low-complexity read-only tool with two parameters and full schema coverage, the description covers purpose and return shape in the absence of an output schema. It could add a note on when to prefer this over create/send task tools, but nothing essential to a correct call is missing.

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?

Schema description coverage is 100%, so eventId and org are already fully documented. The description's 'event's' phrasing lightly reinforces the eventId relationship but adds no parameter-level meaning 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 uses a specific verb and resource: 'List the event's speaker portal tasks' and enumerates the returned fields. This clearly distinguishes it from write-oriented siblings like create_speaker_task and from content lists like list_speakers/list_sessions.

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 verb 'List' implies the intended use—retrieving task data for an event—but the description gives no explicit when-to-use guidance or exclusions. It does not point to alternatives such as create_speaker_task or send_speaker_reminder, leaving the agent to infer selection from naming.

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