get_org_project_item

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

No annotations are provided, so the description carries the full burden. It only says 'Get a single item' with no mention of authorization requirements, error behavior, response structure, or any side effects. It adds no behavioral context beyond what the tool name already conveys.

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 only one sentence plus a documentation link. Every word is functional and there is no redundancy or filler. It is optimally 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?

For a simple single-item fetch with well-documented parameters and no output schema, the description is adequate. However, it could be more complete by noting that this is a read-only operation or referencing the returned item structure. It does not explain what 'item' means or how to use the result, but the purpose is clear enough and the docs link is provided.

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?

The schema provides 100% coverage with descriptions for all three parameters (org, project_number, item_id). The description adds no additional parameter information, but since the schema fully documents them, a baseline score of 3 is appropriate.

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 ('Get') and resource ('a single item in a GitHub ProjectsV2 project'), which distinguishes it from sibling tools like get_org_project (gets the project itself) and list_org_project_items (lists multiple items). It is specific and unambiguous.

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 phrase 'single item' implies use when fetching one specific item by ID, rather than listing. However, it does not explicitly mention when to choose this over list_org_project_items, nor any exclusions or alternatives. The usage context is implied but not fully clarified.

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