github_projects_delete_item_for_org

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

No annotations are present, so the description must convey behavioral traits. It only states 'delete' which implies destruction, but lacks details on permanence, reversibility, required permissions, or side effects. The description does not add 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?

At 5 words, the description is extremely brief. While conciseness is valued, this is too sparse and omits important information. Not every sentence earns its place; the entire description could be expanded to provide more utility without being 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 absence of annotations, output schema, and the complexity of a delete operation, the description is incomplete. It does not explain return values, error conditions, or any consequences of deletion. There is significant room for improvement to make the tool usable without external knowledge.

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 100% (each parameter has a description identical to its name). The description does not add any additional meaning or context about the parameters, such as how to obtain item_id or the format of project_number. Baseline score of 3 applies due to high schema coverage, but no extra value.

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 (delete) and the resource (project item for organization). It distinguishes from sibling tools like github_projects_delete_item_for_user by specifying 'for_org'. However, it doesn't define what a project item is, but the schema makes it sufficiently clear.

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 provides no guidance on when to use this tool versus alternatives (e.g., add_item, update_item). It does not mention prerequisites, permissions, or any context that would help an agent decide to invoke this tool. No exclusions or scenarios are described.

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