get_messages

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It mentions the scope (messages from other agents) but does not disclose whether the tool marks messages as read, ordering, pagination, or any side effects. The description does not even explicitly state it is a read-only operation.

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 exceptionally concise, consisting of two short sentences. It front-loads the core purpose immediately and contains no filler or redundancy.

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?

The tool has six parameters and no output schema, yet the description gives almost no context about return format, filtering behaviors, or default semantics. It does not explain what fields are returned, how messages are ordered, or how 'limit' and 'unread_only' interact. The description is too sparse for an effective agent invocation.

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?

Input schema covers 100% of parameters, so baseline is 3. The description adds no additional meaning to parameters; it only restates the concept of 'messages sent to you' which aligns with 'agent_id'. No parameter-specific insights are provided.

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's purpose: retrieving messages sent to you by other agents. It uses a specific verb ('Get'/'Retrieve') and resource ('messages'), and distinguishes itself from sibling tools like 'get_sent_messages' by specifying the direction (incoming).

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 guidance is provided on when to use this tool versus alternatives, or when not to use it. Sibling tools like 'send_message', 'get_sent_messages', and 'mark_message_read' exist but are not referenced. The context of use is implied but not explicit.

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