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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'retrieve,' implying a read operation, but does not explicitly state that it is read-only or safe, nor does it mention pagination, auth requirements, or any side effects. This is a significant gap for a tool with zero annotation coverage.

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?

A single sentence efficiently states the core purpose. It is front-loaded with the verb and resource, but could have used the spare structure to add usage hints without becoming verbose, so it earns a 4 rather than a 5.

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?

With no output schema and no annotations, the description is the sole source of behavior info. It leaves key gaps: no mention that all parameters are optional, no hint about how omitted agentId resolves, no sense of whether this is a safe read, and no distinction from conversation history. For a tool with 4 optional parameters, this is incomplete.

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 description coverage is 100%, so the baseline is 3. The description adds only the notion of 'specific agent profile,' which maps to agentId, but does not add meaningful semantics beyond what the schema already documents (e.g., default limit, senderType enum, accountId scoping). It neither harms nor significantly helps.

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 verb and resource ('Retrieve recent inbox messages and chat logs') and scopes it to 'a specific agent profile.' However, it does not differentiate from the sibling tool get_conversation_history, which likely serves a similar purpose, so it misses the explicit sibling distinction that would earn a 5.

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 given on when to use this tool versus get_conversation_history or get_message_stats. The description implies usage for recent inbox/chat retrieval but provides no conditions, exclusions, or alternative routing, leaving the agent to infer the right choice.

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