list_messages

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

There are no annotations, so the description is the only source of behavioral context. It merely says 'Get messages list' without disclosing whether this is a read-only operation, whether pagination or filtering exists, or what the returned data structure looks like. No annotations contradict it, but the lack of detail earns a low score.

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 short, but this is under-specification rather than effective conciseness. It says only 'Get messages list' and omits crucial context, making it nearly as unhelpful as a tautological tool description. A concise description should still deliver essential information in a front-loaded manner.

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?

Given no annotations, no output schema, and an empty input schema, the description must carry the full context. It fails to explain what messages are being listed, whether there are filters, or what the response will contain. The sibling tools (e.g., list_groups, list_templates) suggest a set of list operations, but this tool lacks the specificity needed for an agent to reliably select and invoke it.

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 is empty, so there are no parameters to describe. With 0 parameters, the baseline is 4, and the description does not mislead or add unnecessary parameter details. However, it also fails to clarify what messages are being listed, but that is more a purpose issue than a parameter issue.

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 states a clear action ('Get') and resource ('messages'), but 'messages list' is vague and could refer to message templates, conversation messages, or something else. It does not provide enough detail to fully distinguish it from other list-type tools like list_templates or list_groups, though it is the only message-list tool among siblings.

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?

No usage guidance is provided. The description does not indicate when to use this tool versus alternatives, nor does it mention any prerequisites or context in which this list operation would be appropriate. An agent is left to infer based solely on the name.

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