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

Beyond the annotations it discloses concrete behavior: the created punchlist is returned in the same shape as get_punchlist, no users are assigned or notified, and item creation is not supported yet. That is meaningful side-effect context the annotations (readOnlyHint=false, destructiveHint=true, openWorldHint=true) cannot convey. There is mild tension between 'runs without asking' and destructiveHint=true, but no direct contradiction since nothing is described as being destroyed.

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?

Three short sentences, front-loaded with the core action, and each adds a distinct fact (return shape, item limitation, notification behavior). Minor redundancy between 'New, empty punchlist' and 'Adds an empty punchlist' costs it the top score.

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 two-parameter creation tool with no output schema, the description covers purpose, return shape by reference to get_punchlist, side effects, and limitations. What remains uncovered — project existence prerequisites and error behavior — is minor at this complexity.

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%, so both project_id and name are already documented with examples in the schema. The description adds only the loose phrase 'on a project' and no format, validation, or uniqueness detail beyond that. Baseline 3 is appropriate when the schema carries the parameter burden.

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 states a specific verb-and-resource pair (a 'new, empty punchlist on a project') and makes the creation semantics explicit by repeating that an empty punchlist is added and returned. It implicitly separates itself from the item-adding siblings by noting items cannot be added here, though it never names get_punchlist/list_punchlists as 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?

It gives a clear exclusion: items cannot be added through this tool and must be added in Contractor Foreman instead. It also states that no assignment or notification occurs, so it 'runs without asking', which tells the agent it can call it without a confirmation loop. It stops short of naming sibling tools like list_punchlists as a prerequisite check.

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