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

Annotations already declare readOnly, idempotent, non-open-world, non-destructive, so the safety profile is covered. The description adds meaningful behavioral context beyond that: owner-only scoping, reliance on live task due/done state, and the warning that page membership can change, plus an explicit guarantee that no message or Calendar change is sent.

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?

Three short sentences, front-loaded with the purpose and followed by behavioral caveats; nothing is redundant. The phrasing is terse to the point of being cryptic in places ('matches the app view'), but it wastes no space.

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 three-required-parameter list tool with no output schema and 0% schema description coverage, the description covers purpose and mutation-safety well but leaves the parameters entirely undocumented. An agent knows what the tool is and that it is safe, but not how to correctly drive the view/cursor/limit arguments.

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 0% across three required parameters and the description does not compensate. 'Matches the app view' loosely hints that the view parameter mirrors the app's tabs, and 'page membership can change' hints at pagination, but the cursor semantics of 'after', the meaning of each enum value, and the 1-50 limit bound are left entirely unexplained.

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 names a specific verb and resource: reads owner-only in-app meeting prompts or due follow-up tasks. It is clearly differentiated from write siblings like book_meeting or cancel_booking, though it does not distinguish itself from list_bookings or list_sales_tasks, which are the nearest alternatives.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. An agent must infer from 'owner-only' and the view enum (upcoming/outcomes/due) when this list is the right one versus list_bookings or list_sales_tasks.

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