get_group_items

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

No annotations are provided, so the description carries the full burden. It does disclose the one genuinely important trait — cursor-based pagination — and 'List' implies a non-mutating read, but it says nothing about result ordering, default page size behavior, or what happens when the cursor is exhausted.

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?

A single front-loaded sentence with no filler; the pagination caveat is placed inline where it is immediately useful. Nothing in the sentence could be removed without losing information.

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 values need not be described. But for a two-required-identifier tool with 0% schema coverage and no annotations, the description is too thin — it never clarifies the board_id/group_id relationship, page size limits, or iteration workflow.

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% — all four parameters have only bare titles. The description's '(cursor-paginated)' hint partially covers the cursor parameter, but board_id, group_id and limit (default 50, presumably a max) are left entirely undocumented, including why board_id is required alongside group_id.

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?

States a specific verb ('List') and a precisely scoped resource ('items that belong to a group'), which implicitly separates it from list_items, get_items_by_tag and search_items. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than declared.

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 group-scoped framing implies when this tool applies, but there is no explicit when-to-use guidance, no mention of when to prefer list_items or get_items_by_tag instead, and no stated prerequisites (e.g. that board_id and group_id must both be known).

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