support_read

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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description adds little beyond restating the mutation. It does not explain what marking as read changes, whether the effect is user-visible, whether it can be undone, or how it relates to the surprising destructiveHint=true flag; the only new fact is the REST endpoint. There is mild tension between "mark as read" (a low-impact state toggle) and destructiveHint=true, though it does not rise to a direct contradiction.

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?

Two short lines, front-loaded with the action, followed by the endpoint. Nothing is padded, though the raw HTTP path is of limited use to an agent and the description could have spent that space on behavior instead.

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 mutation tool with a fully undocumented parameter and no output schema, the definition omits the essentials: what the returned result looks like, whether failures are silent for unknown IDs, and any permission requirements. Annotations cover the safety profile, but the description should carry more of the operational detail.

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 the single 'id' property, so the schema alone gives no meaning. The description's path template {id}/read at least establishes that 'id' is the ticket identifier used in the URL, but it says nothing about valid ranges, formats, or what happens with a nonexistent 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?

"Mark ticket as read" gives a specific verb (mark) plus the state change (read) on the ticket resource, which resolves the ambiguity of the tool name support_read (which could suggest fetching a ticket). It does not distinguish this from siblings like support_get_one or notifications_mark_as_read, but the core action is unambiguous.

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 versus support_get_one, support_archive, or support_send_message, and no stated prerequisites such as needing the ticket to exist or be assigned. The only hint is the POST path, leaving the agent to infer context entirely.

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