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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description does add genuinely new behavioral context — MCP approval requirements are org-configurable and business workflow approvals always apply — which warns the agent that a call may be gated. It says nothing about pagination limits or result ordering, though.

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 sentences, no severe bloat, but the actual purpose is buried in the middle behind a generic context preamble. The trailing approval sentence is longer than the functional description it follows.

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 need not be explained. But for a paginated list tool with four undocumented parameters, the description omits pagination behavior, default limits, and search semantics — real gaps an agent must infer from the schema constraints alone.

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% for all four parameters, so the description carries the full burden. It only implies siteId scoping via 'site punch-list items' and adds no meaning for limit, offset, or search (e.g., what fields search matches against), leaving the agent to guess.

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 middle sentence states a specific verb and resource: 'Read site punch-list items,' which clearly distinguishes it from mutation siblings like create_punch_item or delete_punch_item. However, nothing distinguishes it from list_checklist_items or get_punch_item, so sibling differentiation is only partial.

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?

The only usage framing is 'when working with RetailHardHat field_operations records in the connected organization,' which is boilerplate scoping rather than a real use condition. There is no guidance on when to list versus call get_punch_item, nor how to use search/offset to narrow results instead of listing everything.

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