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

Annotations already flag a non-read-only, non-destructive, non-open-world mutation, so the description's real value is the disclosure that no change occurs until a human approves the exact request and execute_approved_action is called, plus that approvals are admin-configurable. This is exactly the kind of beyond-schema behavior an agent needs. It stops short of noting non-idempotency (idempotentHint=false), which would have earned a 5.

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?

It's reasonably short, but the opening sentence is filler that delays the actual purpose to sentence two. The approval-workflow sentences are valuable and worth keeping, so the waste is limited to the generic framing rather than 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?

An output schema exists, so return values needn't be explained, and the approval-gating behavior is covered. However, for a nested mutation with 0% parameter documentation, the description omits anything an agent needs to construct the 'data' payload correctly, leaving a real gap.

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% across a nested 'data' object with title, trade, status, severity, dueDate, vendorId, assignedToUserId, and more, plus a required siteId. The description says nothing about any of these — not the required title, not the enum meanings, not the UUID format for siteId — so an agent gets no semantic help for a fairly complex payload.

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 second sentence, 'Create a punch-list item,' gives a specific verb and resource that separates it from update_punch_item, delete_punch_item, and get_punch_item. The opening 'RetailHardHat field_operations records' sentence is generic scaffolding that doesn't add specificity beyond the name. It's clear but lacks explicit sibling differentiation in the description itself.

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?

'Use this when working with RetailHardHat field_operations records in the connected organization' is vague and amounts to 'when you need this record type' — it does not state when to create vs. update a punch item, nor any preconditions for choosing this tool. The approval-workflow sentences describe mechanics, not selection guidance or exclusions.

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