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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond restating the action: it does not explain what 'read' changes, whether it affects unread counts or notifications, or whether the case must be yours.

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?

A single compact sentence with no filler, and the action is front-loaded. It is under-specified rather than padded, so conciseness itself is fine.

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 one-parameter, non-destructive mutation whose annotations already convey idempotency and safety, the description is close to sufficient. It falls short on the sole parameter's semantics and the absence of any usage routing, but nothing critical is misleading.

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 coverage is 0% for the single required caseId parameter, and the description offers no format or source detail beyond the vague 'one of your support requests'. It does not clarify the `^[A-Za-z0-9_-]{1,200}$` pattern or where to obtain the ID.

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 ('Mark ... as read') and resource ('support requests'), which is clear and distinct from siblings like get_support_case or reply_to_support_case. It does not explicitly contrast itself with those siblings, keeping it below 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?

No guidance on when to use this versus get_support_case, list_support_cases, or reply_to_support_case, and no prerequisite noted (e.g., that caseId must come from an existing case). Usage is only implied by the verb 'Mark ... as read'.

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