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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'get', which implies read-only, but does not disclose authentication needs, rate limits, whether messages are marked as read, or what 'recent' means (e.g., time window). This is a significant gap for a tool with no annotation support.

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 that directly states the tool's function. Every word contributes to meaning, and there is no wasted content.

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 simple getter with 4 parameters, the description is minimally adequate but lacks return value details, ordering, pagination, and usage context. With no output schema or annotations, more contextual guidance would be expected, such as indicating that limit controls count and that topic is an optional filter.

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 baseline is 3. The description adds context by mentioning 'room/topic', but this is ambiguous given that roomId is required and topic is optional. It does not clarify that roomId is mandatory or how topic relates to room, potentially misleading the agent.

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 'Get recent messages from a room/topic' clearly identifies the action (get), resource (messages), and scope (room/topic). It is specific and distinguishes this tool from sibling tools like nolag_get_room or nolag_list_rooms, as no other sibling targets messages.

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 implies usage when recent messages are needed, but provides no explicit when-to-use guidance or alternatives. It does not mention exclusions (e.g., historical messages, other scopes) or contrast with related tools like nolag_publish or nolag_list_agent_events.

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