Create punchlist

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

Adds real context beyond the annotations: the created object is empty, it cannot be populated here, no one is assigned or notified, and it can run without confirmation. Those are exactly the side-effect facts an agent needs. It does not address what happens on duplicate names or whether repeats create multiple punchlists, despite idempotentHint=false.

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?

Short and front-loaded, with the scope statement first and limitations after. The opening sentence is a fragment ('New, empty punchlist on a project.') that reads slightly as a title restatement rather than a full clause.

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?

With no output schema, the description compensates by saying the result is what get_punchlist returns, and it covers side effects and limitations. Only re-creation behavior for non-idempotent calls is left unexplained.

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 coverage is 100%, with both project_id and name documented in the schema, so the baseline applies. The description adds only the 'empty' characteristic and no naming or format guidance for the two parameters.

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?

States a specific verb and resource ('Adds an empty punchlist to the project') and scopes it with 'empty', which differentiates it from get_punchlist/list_punchlists. It references get_punchlist only to describe the returned shape rather than to route the agent, so sibling differentiation is implied rather than explicit.

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?

Gives a clear when-not: items cannot be added through this tool, they must be added in Contractor Foreman. That is actionable context an agent would otherwise have to guess. It stops short of naming sibling alternatives such as list_punchlists or get_punchlist for follow-up.

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