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

Annotations provide only a title, so the description carries the behavioral burden. It clearly indicates a read-style list operation scoped to the caller, but it does not disclose pagination behavior, authentication requirements, response shape, or any side effects. The core behavior is present, but meaningful behavioral details are missing.

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, front-loaded sentence with no wasted words: the verb, resource, and scope appear immediately. It is appropriately concise, though it is terse enough that it leaves out important behavioral and parameter context.

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 tool with two undocumented pagination parameters, no output schema, and only a title annotation, this description is not complete enough. It explains the high-level action but omits how 'limit' and 'offset' behave, what the caller owns, and what a successful response looks like. An agent would need to guess or inspect elsewhere before using it confidently.

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 0% and both 'limit' and 'offset' have empty descriptions. The tool description does not mention these parameters at all, so an agent receives no explanation of how to use them, what units they use, or whether defaults apply. The description fails to compensate for the complete lack of parameter documentation.

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 specific verb ('List'), a specific resource ('stored message ids'), and a clear scope ('owned by the caller'). It reads as a distinct plural listing operation and is distinguishable from the sibling 'chat_source' tool by both name and the ownership qualifier.

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 about when to use this tool versus alternatives like 'chat_source', 'chat_messages', or 'chat_rooms'. The ownership scope is implied by 'owned by the caller', but the description never states when this tool is preferred or when another chat-related tool should be used.

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