list_project_items

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read profile is covered. The description adds one useful behavioral note: that content bodies are excluded from results. However, it doesn't mention pagination behavior or how limit interacts with large projects, which would be valuable context for a list operation with a default limit of 30.

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?

Two sentences, zero wasted words. The first sentence states the purpose precisely, and the second sentence adds one crucial exclusion. Every word earns its place in this description.

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?

The tool has 5 parameters (0% schema described), no output schema, and no nested details explained. The description is a list operation with clear read-only annotations, which is relatively simple, but with no output schema and no param explanation, the description leaves the agent to infer what 'metadata' means and how the 5 parameters map to the query. Adequate for a simple list tool but incomplete on parameter semantics.

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%, so the description carries the compensation burden for 5 parameters. The description identifies the resource being listed (issues/PRs) which maps to projectId, account, owner, but it does not explain what each parameter represents or clarify the distinction between account and owner. With 0% coverage, the description should do more to clarify parameter semantics.

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+resource: 'List Issue and Pull Request metadata in a GitHub Projects v2 project.' Clearly distinguishes from siblings like add_project_item, set_project_item_field, and list_project_fields. The scope of what is listed (issues and PRs) and the project type (Projects v2) are explicit.

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 clarifies that field values and content bodies are not returned, which sets expectations for what data the agent will (and won't) get. However, it doesn't provide explicit guidance on when to use this vs alternatives like list_issues or list_pull_requests, nor does it mention the relationship to list_project_fields for retrieving field values.

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