github_projects_add_item_for_user

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

With no annotations, the description should disclose behavioral traits. It only states the action without mentioning that it is a mutation, what happens on success/ failure, or any side effects. The vague 'body' parameter is not explained, leaving critical behavioral gaps.

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?

The description is very concise (one sentence) and front-loaded, which is good for readability. However, the brevity sacrifices informativeness; some additional detail would improve completeness without being overly verbose.

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?

Given the complexity of GitHub projects (many sibling tools, no output schema), the description is insufficient. It does not explain what an item is, how to find the project number, or the required format of the request body. This leaves significant gaps for an agent to use the tool 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 coverage is 100%, so the baseline is 3. The description adds no extra meaning beyond the schema's parameter names and minimal descriptions. For example, the 'body' parameter is not explained in terms of expected structure or required fields.

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 verb 'Add' and resource 'item to user owned project', indicating the action and scope. However, it does not elaborate on what constitutes an 'item' (e.g., issue, pull request, note) or how it differs from sibling tools like adding fields or draft items, which slightly reduces clarity.

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 is provided on when to use this tool versus alternatives such as github_projects_add_item_for_org or github_projects_create_draft_item_for_authenticated_user. The description lacks context on prerequisites, limitations, or use cases, making it difficult for an agent to decide when to invoke this tool.

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