project_list_items

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

No annotations are present, so description must fully disclose behavior. It only says 'List all items' without mentioning pagination limits, rate limits, or side effects. The agent cannot tell if this is a read-only operation, if it returns all items or paginated, or what happens for large projects.

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?

Single sentence with no redundancy. It is front-loaded with verb and resource. Could be improved by adding structure like listing scope or output format, but as a minimal statement it is concise.

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?

Missing crucial context for a list tool: no output schema, no mention of pagination, sorting, or whether returned items include IDs. The description says 'status and metadata' but these are not defined. Given many sibling tools, more detail on what is returned is needed for agent decision-making.

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 100% with descriptions for all four parameters. The description adds no additional meaning beyond schema; 'status and metadata' loosely connects to optional filters but doesn't explain parameter values or constraints. Baseline is 3 given high schema coverage.

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 clearly states the tool lists items in a GitHub Project V2 with status and metadata. The verb 'List' and resource 'items in a GitHub Project V2' are specific. It distinguishes from sibling tools like project_add_item (adds items) and project_get_issue (gets single issue), but could be more explicit about scope.

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?

No guidance on when to use this tool vs siblings like project_backlog_report or project_list_fields. The agent has no basis to choose between listing items here vs other project listing tools. No exclusions or best uses mentioned.

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