mark_conversation_read

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 a genuinely non-obvious side effect – that a complete read also dismisses Talk notifications – plus the return shape, which goes beyond the structured data.

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 side-effect sentence is front-loaded and the Args/Returns blocks are compact. Slightly more structure than strictly needed for two parameters, but nothing is wasted.

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 two-parameter mutation with annotations covering safety and an output schema covering return values, the description supplies the missing pieces: the partial-vs-complete semantics and the notification side effect. Adequate and nearly complete.

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%, so the description must carry the load, and its Args section documents both parameters, notably explaining that message_id default 0 means 'everything'. The token entry is thin ('The conversation token'), but the effective meaning of the optional parameter is clearly conveyed.

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+resource ('Mark a conversation as read') and immediately clarifies the two modes (up to a message vs. completely). An agent can distinguish this from the sibling mark_conversation_unread without opening a schema.

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 'up to a message or completely' clause implies how to use the message_id parameter, but there is no explicit when-to-use guidance, no prerequisite statement, and no routing to the obvious alternative (mark_conversation_unread). Usage is implied rather than stated.

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