list_github_project_items

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds only the note that the project must be 'authorized', and omits pagination behavior despite a 'first' parameter, which the annotations do not cover.

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 tight sentence with the returned entities front-loaded. Efficient, though its brevity is part of why usage and parameter guidance are absent.

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?

No output schema is needed for a read-only list tool and annotations cover safety, but the description leaves parameter formats and pagination unexplained. It is minimally adequate for a list operation but misses context an agent needs to invoke it correctly.

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 parameters (owner, number, first). The description adds no meaning for any of them — no format for owner, no explanation of number, and no disclosure that 'first' controls pagination/batch size.

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?

Specific verb 'List' paired with a well-defined resource set (issues, pull requests, draft issues, assignees, field values) scoped to an authorized GitHub Project v2. An agent can distinguish it from list_github_projects and list_github_project_fields, though it never names a sibling 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?

The description states what the tool returns but gives no when-to-use guidance, no prerequisites, and no alternatives (e.g. resolve_github_project_item or get_github_project_snapshot). Selection must be inferred entirely from the name.

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