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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds only the vague 'authenticated' scope qualifier and says nothing about pagination, ordering, or what the response contains — behaviorally important for a list endpoint.

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 short sentence with zero filler, and the verb/resource is front-loaded. It is efficient, though its brevity leaves it under-specified rather than genuinely concise.

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 listing tool with a pagination-limited parameter and no output schema, the description should at minimum say what a page contains, ordering, or how to page further. None of that is present, so an agent must guess at result semantics.

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 the single `limit` parameter is never mentioned in the description. The schema does supply type, default (20), minimum and maximum, so the agent can call it, but the description adds no meaning beyond the schema.

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 concrete verb+resource ('List ... support conversations'), which cleanly separates it from support_messages_list and support_conversation_create. However, it never explicitly contrasts itself with those siblings; the distinction has to be inferred from the noun.

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 call this versus support_messages_list (messages for a conversation) or the other support_* tools, and no mention of prerequisites such as needing an authenticated session. The word 'authenticated' hints at a precondition but doesn't state one.

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