messages_list

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. Saying 'Message center list' conveys little beyond the operation name; it does not state whether the call is read-only, what scope of messages is returned, or whether any state is affected. The read-only nature is implied by 'list' but never made explicit.

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 description is extremely brief but it is closer to under-specification than useful conciseness. It is a fragment rather than a complete operational description, and it provides no structural detail such as inputs, scope, or exclusions. Being short is not valuable when so little information is conveyed.

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?

Because the tool has zero parameters and an output schema is present, the minimal description is enough to guess a basic invocation. However, the description lacks context about what 'message center' means, how this list behaves, and how it differs from nearby messaging siblings, leaving the agent to rely on inference.

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?

The input schema declares zero parameters and schema description coverage is 100%, so there are no parameter semantics to explain. Per the rubric, this yields a baseline of 4, and the description does not need to elaborate on parameters that do not exist.

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?

Message center list" clearly indicates this tool returns a listing of message-center items, and the name messages_list reinforces the resource. It does not explicitly differentiate itself from the sibling messages_get, but list versus get is a recognizable distinction. The main gap is the absence of any detail about what messages are included or excluded.

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 description gives no guidance on when to choose this tool over messages_get, tickets_list, or any other messaging-related sibling. It neither states an intended use case nor rules out alternatives, so an agent must infer the usage from the tool name alone.

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