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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower. The description adds behavior annotations do not carry: result ordering ('newest meeting first'), the default status filter, and that each item carries its source meeting. Pagination behavior is not disclosed.

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 dense sentences with the ordering and default-filter facts front-loaded; every clause conveys distinct information and nothing is padded.

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?

An output schema exists, so return-value documentation is not required, and the description still notes that items carry their meeting. Filters, defaults, and ordering are covered; the only real gap is pagination guidance around limit (default 50) and cursor.

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 coverage is 60%, and the description fills the biggest gap: meeting_id has no schema description, yet the text explains it filters to 'a single meeting'. It also clarifies the status default ('open by default'), though limit and cursor remain unexplained in both places.

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 states a specific verb and resource ('List the user's action items across meetings') and even specifies scope ('across meetings, newest meeting first'). It is clearly distinguishable from siblings like list_meetings or get_meeting, though it never explicitly names an alternative tool.

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?

Usage is implied through defaults ('open by default, or done, or all') and the filtering options, which helps an agent choose a status value. However, there is no explicit when-to-use versus alternatives guidance, nor any mention of the sibling tools (update_task, complete_task) that mutate these items.

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