get_conversation_controls

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

The description states 'Opening may mark read,' which is a state mutation, directly conflicting with the readOnlyHint=true annotation asserting the tool does not modify its environment. Although it also discloses genuinely useful behavior (unsupported layouts return an error rather than guessed capabilities), the presence of an annotation contradiction forces a 1.

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 tight sentences, front-loaded with the purpose and followed by the caveats, with no filler. Efficiency is good; only the density of undefined jargon keeps it from a 5.

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 the description does add behavioral caveats (error on unsupported layouts, possible mark-read). But with both required parameters wholly unexplained, the definition is not complete enough for confident invocation. Minimum viable.

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% and there are two required parameters (account, conversation_id) that the description never explains. The only hint is the phrase 'conversation-menu', which loosely maps to conversation_id but leaves 'account' and the identifier formats entirely undocumented. The description does not compensate for the coverage gap.

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 pairs a verb ('Inspect') with a resource ('visible request and conversation-menu controls'), giving a workable if jargon-heavy sense of what it does. However, it offers no differentiation from close siblings such as get_conversation or manage_conversation, so an agent cannot easily tell which one to reach for. Adequate but with clear gaps.

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 explicit when-to-use guidance, no named alternative, and no prerequisites or preconditions stated. The reader is left to infer the tool's role in the conversation flow entirely from the name. Only mildly implied usage, so a 2.

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