Listar mensajes

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

Annotations already provide readOnlyHint (safe) and openWorldHint (incomplete results). The description adds ordering (newest to oldest) and filtering options, which are useful behavioral details. No mention of pagination or rate limits, but annotations cover safety, so this is sufficient.

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 a single sentence that efficiently conveys the main action and filters. It is front-loaded with 'Lista los mensajes enviados' and includes all key points without waste. Could be slightly improved by splitting into two sentences.

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 read-only list tool with good annotations and no output schema, the description covers purpose, ordering, and filtering. It does not explain the return format or pagination behavior, but these are not critical given the tool's simplicity and the limit parameter hint.

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 coverage is 100% with detailed descriptions for all 4 parameters. The description only repeats the parameter names (broadcast, status, metadata) without adding new semantics beyond what the schema already provides. Baseline 3 is appropriate.

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 sent messages in reverse chronological order. It specifies the resource (messages) and the ordering, distinguishing it from siblings like hilo_get_message (single message) and hilo_list_broadcasts (broadcasts).

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 mentions filtering capabilities (by broadcast, status, metadata), indicating when to use this tool. However, it does not explicitly state when not to use it or mention alternatives like hilo_get_message for single messages. Still, context is clear.

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