set_project_item_field

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

Annotations include readOnlyHint=false, idempotentHint=true, destructiveHint=false. The description adds nothing beyond this beyond naming value types. It does not disclose how partial values behave, what happens on invalid valueType, whether setting a field requires existing field of that type, or how iteration/date values are formatted. With no additional behavioral context provided, the burden falls on the description, which remains thin.

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 efficient sentence with no wasted words. It front-loads the action and resource. However, it is under-specified rather than concise in a maximal way — it could carry more useful content without bloat.

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?

This is a complex mutation tool with 8 parameters, 7 required, 0% schema coverage, and no output schema. The description covers the value types but omits crucial operational details: how to obtain fieldId (via list_project_fields), what value formats each valueType expects, behavior on invalid inputs, and whether the mutation is per-field only. For a write operation with this complexity and zero parameter documentation, the description is insufficient.

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 0%, so the description must compensate. It lists the supported value types (text, number, date, single-select, iteration), which maps to the valueType enum. However, it does not explain the relationship between value and valueType (e.g., how dates should be formatted, how singleSelect values map to field options, how iteration references work). The fieldId, itemId, projectId semantics are entirely undocumented beyond their regex patterns in the schema.

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 a specific verb ('Set') with a specific resource ('text, number, date, single-select, or iteration value on a GitHub Projects v2 item'). It names the supported value types and identifies the domain (GitHub Projects v2). It distinguishes from siblings like clear_project_item_field, though it doesn't explicitly name alternatives.

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 vs set_project_item_archived, add_project_item, or list_project_fields. The description does not explain when one would set a field value versus using alternatives, nor any prerequisites (e.g., needing fieldId from list_project_fields, needing itemId from add_project_item).

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