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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, closed-world), so the description's value is in what it adds: the default pending filter and the shape of each record (priority, status, owner, due date). It does not mention pagination or the 100-item cap implied by the limit parameter, which is the main remaining gap.

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 front-loaded sentence names the resource, parenthetical examples clarify intent, and a short trailing clause states the default. No filler, though the examples and the field list make it slightly denser than the minimum needed.

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 simple read-only list tool with no output schema, the description compensates by enumerating the returned fields and the default filter. The only meaningful omission is the result-count behavior controlled by limit, which leaves an agent guessing about paging.

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 50%: the status parameter is documented with its default enum list, while limit (1-100) is undocumented in both schema and description. The description's 'Default: pending items' mostly restates the status default already in the schema and adds no syntax or cap information for limit.

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 resource (action items RivalSweeper raised for your team) and concretizes it with two examples (fix a broken ad landing page, respond to a rival promotion). It implicitly separates itself from data-inspection siblings like get_competitor_moves_feed by framing these as assigned team to-dos, though it never names an alternative explicitly.

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?

'Default: pending items' tells the agent what it gets without arguments, which is genuine usage context, but there is no guidance on when to call this versus the many sibling analysis tools, and no stated exclusions or prerequisites.

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