github_projects_get_user_item

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

No annotations are provided, and the description does not disclose behavioral aspects like authentication requirements, error handling (e.g., missing item), rate limits, or any side effects. Since annotations are absent, the description carries full burden but fails to address these.

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 with no extra words. It is front-loaded and efficient. However, it could include a bit more structural detail without becoming verbose, but overall no waste.

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 tool has 4 parameters and no output schema, the description is insufficiently complete. It does not explain what an 'item' is, the return value structure, or any constraints (e.g., project must be user-owned). More context is needed for an agent to use it 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?

The input schema has 100% coverage with basic descriptions (e.g., 'username' for username). The description adds no additional meaning beyond the schema, such as format expectations or relationships between parameters. 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 'Get an item for a user owned project' uses a specific verb (Get) and resource (item), and clearly indicates the scope (user owned project). It distinguishes from sibling tools like 'github_projects_get_for_user' (which gets the project itself) and 'github_projects_get_org_item' (for org projects).

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, such as when to use on org projects or how it differs from fetching the project itself. No exclusionary or contextual hints are given.

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