github_projects_create_draft_item_for_org

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

No annotations provided. The description does not disclose any behavioral traits such as mutation, required scopes, or side effects. Without annotations, the description carries the full burden, but it fails to provide context beyond the basic action.

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 a single concise sentence. While efficient, it lacks structure (e.g., no separate sections) and could be more informative without exceeding acceptable length.

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 no output schema and no annotations, the description is incomplete. It does not explain what a draft item is, how the body should be structured, or what the response will be. For a tool with nested objects, more context is needed.

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 has 100% coverage but descriptions are just param names ('org', 'project_number', 'Request body (JSON object)'). The tool description adds no additional meaning. The body parameter is an object but its structure is unspecified, leaving the agent without guidance on required or optional 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 action (Create draft item) and scope (for organization owned project). However, it does not distinguish from sibling tools like github_projects_add_item_for_org, which adds an existing item to a project. The name already implies 'draft', so the description adds little differentiation.

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 versus alternatives like add_item. No preconditions (e.g., project must exist, auth requirements) are mentioned. Usage context is implied only by the name.

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