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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear without description help. The description adds approval-related context ('MCP approval requirements are configurable... business workflow approvals always apply'), which is useful but vague and not clearly tied to this read operation.

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 definition is short and front-loads the core action in the first sentence. The second sentence is somewhat tangential but still provides relevant approval context, so the description remains appropriately sized.

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 described, and annotations cover safety and idempotency. However, the description leaves gaps for an agent: it does not explain the required siteId parameter or when this list operation is preferable to sibling tools such as list_checklist_items or get_opening_record_details.

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?

The input schema has 0% description coverage and the description never mentions siteId or what value it should contain. The word 'site' hints that a site identifier is involved, but the description adds no meaning about the required UUID parameter or its role in scoping the checklist results.

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: 'Read site opening checklists.' This is clearer than a mere restatement of the name and tells the agent it is listing/reading site-scoped opening checklists. It does not explicitly distinguish the tool from nearby siblings such as list_checklist_items or get_checklist_template, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus alternatives like list_checklist_items, get_checklist_template, or get_opening_record_details. The second sentence discusses approval configuration but does not explain when this tool should be selected or avoided.

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