list_messages

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

No annotations are provided, so the description must disclose behavioral traits. It mentions ordering ('most recent first'), pagination limits (default 25, max 100), and auth requirement ('messages:read capability gate'). However, it does not discuss behavior for invalid order IDs, rate limits, or complete response structure. The output schema exists but is not referenced.

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 short and front-loaded with purpose. Each sentence adds value, though the phrase 'on a title order' is unclear and slightly distracting. Overall, it is concise without unnecessary words.

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 the two parameters and presence of an output schema, the description covers key aspects: purpose, ordering, auth, and parameter details. It could clarify whether 'buyer side' implies filtering, and what 'title order' means, but it is largely complete for typical use.

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 schema has no descriptions (0% coverage), so the description must provide parameter meaning. It explains order_id as 'the Qualia order id' and limit as 'page size (default 25, max 100)', adding useful context beyond type and default.

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 clearly states the tool lists messages on an order with most recent first, and provides example use cases. However, the phrase 'on a title order' is ambiguous and appears to be a typo, slightly reducing clarity.

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?

Explicit use cases are given ('what's the latest message on this order?' or 'show all messages from the buyer side'), guiding appropriate invocation. It does not explicitly state when not to use or compare with siblings, but the context is sufficient.

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