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

Goes well beyond the annotations (readOnly=false, destructive=false, openWorld=true) by disclosing that the item is assigned to another person, that the call reaches other people and must be confirmed with the user each time, that a due date lands on the calendar, and that an app-scoped API key is needed. This is exactly the extra context annotations cannot carry.

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 confirmation requirement is stated three times in near-identical wording ('so you confirm it', 'By default you confirm each call', 'confirm with the user before each call'), and the opening clause duplicates the title. Front-loading is fine but the repetition costs it.

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 4-parameter mutation with no output schema, the description covers side effects, the human-approval gate, and auth needs. Only minor gaps remain, such as what the response contains or failure behavior when the assignee is not in the Directory.

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 all four parameters (title, assignee, due_date, project_id) are already documented in the schema. The description restates assignee-from-Directory and due-date-to-calendar without adding format or constraint detail, so baseline 3 applies.

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 a punchlist item to the project') plus the assignment and calendar side effects, which an agent can distinguish from siblings like create_daily_log or create_change_order. The opening sentence largely restates the title, so it is clear rather than exemplary.

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 concrete operating context: confirmation is on by default and can be switched off for this tool, and the user's Cotlet API key with app access is required. It does not name alternatives (there is no sibling punchlist tool to route away from), so it stops short of explicit when/when-not guidance.

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